Skip to main content

Generic shapes this fabric supports

Deep end

The public shapes are on use cases. This page is the catalogue: caller, control-flow, composition, and the seed proofs that illustrate them. Autonomy integers live in autonomy.

Domain-agnostic caller, control-flow, and composition shapes. Seed routes (fee_explain, purchase_refund, …) are proofs — not the product list.

Jobs vs chat is ingress, not a shape on this page. Autonomy mode does not invent a fifth document or human-review shape.

Caller and control-flow​

Detail pages in this section. One concern per page.

ShapeConcernDetailNow
Document by enterprise idDMS already holds the object; JSON carries doc_id (or short-lived GET)files-via-dmsJSON doc_id yes; real DMS GET mocked
Document via channel uploadMultipart → Front Door PUT → mint id → same JSON pathfiles-bytes-uploadNot built (ingress_files)
Review evidence (no pause)Classify emits structured human_review_* for a later branch or reviewerhuman-review-llm-signalSchema + notes yes; slot/branch consumers see autonomy modes
In-run process gateDesigner human_gate → waiting → resume → requires_approval writehuman-review-process-gatePause/resume runs
Async human handoffDomain escalate_to_human → ticket id → parent completedescalate-to-human-handoffPattern 1 auto-complete + idempotent re-CALL runs

Default document path: DMS-first. Default risky write: process gate. LLM signal never pauses by itself. Ticket-and-done is not a gate.

Autonomy product shapes​

Who picks the next step. Full contracts: autonomy.

ModeGeneric productTypical work
0 — single inferenceOne LLM reply, no toolsSummarize pasted text, greeting, policy-style chat without HTTP
1 — autonomous loopLLM CALL / DONE over a manifestLookup Q&A, research, multi-tool investigation, specialist fan-out
2 — deterministic pipelineFixed workflow stagesPrefetch → act, OCR → classify → eligibility → write, risk branch
3 — guidedStaged path; allowlist named on the routeTriage/draft, counsel-style review (allowlist catalogue-only today)

Orthogonal attachments​

Compose beside autonomy_mode. Not new modes. See patterns README.

AttachmentGeneric capability
RetrievalPack corpus before generate, or model/tool CALL retrieve
Slots / schema handoffPrior stage JSON → next HTTP only where input_schema allows
kind=agent childStart another catalogue route as a job (projected payload)
Subagent joinParent waits for specialist(s), then continues
Checkpoint resumeFailed run continues from resume_index
Side-effect latchside_effect + requires_approval after a human packet

Platform shapes (not separate 07 files)​

ShapeRoleTrack
Named jobs bindCaller supplies route_id; entitle → pin → runtodo
Chat decideUtterance → route / clarify / abstain (rules + retrieve)intent; Layer ③ LLM fallback deferred
Audit evidence chainDecide → freeze → stages → terminal (incl. waiting)audit
Generic tool failureBusiness/technical envelope → retry / observe / escalate / fail_runtool-failure — in flight
Gate SLA timeoutDesigner on_timeout on human_gateDesigned on process gate; not built
Shared MemoryReal conversation / long_term storesfuture-enhancement

Seed → generic map​

Seed proofGeneric shape
email_summarizePattern 0 synthesis
fee_explainPattern 1 lookup loop
msa_risk_review / contract_reviewDoc-id intake → retrieve/score → memo
purchase_refundExtract → LLM signal → process gate → write
kyc_onboardingScreen → branch → gate or activate
shopassist_caseLocator ASK → domain APIs → async escalate → complete
fraud_investigate / ops_start_kycParent starts child agent job
policy_memo / pack_then_*Prefetch pack then act/generate

Not on this page​

TopicWhere
Full Pattern 0–3 contracts and illegal combinationsautonomy
Stage data (goal / slots / notes)data