Intake
Normalize the request, rail, workflow type, inputs, callback preference, and requested return package.
Wever Labs structures agent work beyond one-shot prompts. Each rail moves through a operating cycle: intake, planning, specialist work, validation, exception handling, revision, review, return package, and attestation.
The orchestrator maintains loop state and sends work through specialized agents. Every step writes an agent operator-visible record so the return package is inspectable rather than mysterious.
Normalize the request, rail, workflow type, inputs, callback preference, and requested return package.
Planner agent maps the work to success criteria, required evidence, and rail-specific output objects.
Specialist agent produces the manifest, reconciliation, readiness object, risk summary, notice package, or draft discovery submission.
Validator checks required fields, evidence coverage, schema shape, review rules, and return-package readiness.
Exception objects, revision feedback, review state, result contract, receipt, callback, and attestation close the loop.
Each rail keeps its own domain logic, but the loop frame stays consistent enough for agents to understand and reuse.
Build manifest, check required items, detect missing items, create readiness and exception objects.
Open PacketOps loop →Normalize records, match evidence, identify exceptions, issue receipt, prepare attestation.
Classify project context, check evidence, name missing items, return packet state.
Inventory evidence, draft risk summary, report missing items, score readiness, create attestation.
Open example →Bind workflow scope, check evidence, produce result contract, usage receipt, ledger reference, and attestation.
Check holder records, prepare notice readiness, export readiness, exceptions, and audit trail.
Discover target, classify fit, draft discovery submission, review review, wait for agent operator decision.
Open example →Scope obligations, renewal dates, clause exceptions, redline questions, and agent operator-reviewed return packages.
Open draft contract →LoopCore v1 adds public schemas, examples, and a GET/POST endpoint so agent builders can inspect the operating loop before submitting rail work.
Use the Agent principal Activation Path to choose PacketOps or DiligenceOps and run one narrow proof-backed workflow before expanding into the full rail shelf.