Intent finds the requirements buried in your repository and supporting documents. It recommends which verifiers should check them. Your team decides what to run.
Assurance contracts
Context files can give agents useful background. But assurance needs more than guidance. It needs organizational requirements connected to explicit rules for where they apply and how they are evaluated.
Requirements are scattered across code, documents, and conversations. Intent brings those sources together and shows where each proposed requirement came from.
Code, tests, schemas, configuration, documentation, and implementation patterns.
Policies, design documents, specifications, operating procedures, and runbooks.
Selected channels and threads that provide context around operational requirements and exceptions.
Bring policies, PDFs, DOCX files, Markdown, text, and other artifacts directly into discovery.
Intent looks for behavior your service depends on and drafts requirements for your team to review. Each draft points back to the material behind it.
Intent gathers specific, traceable signals from the connected sources.
Repeated requests with one idempotency key produce a single charge.
Refund Policy.docx requires manager approval above a stated threshold.
Invoice service compares line-item sum against final invoice total.
Selected Slack thread documents a narrow exception to the normal workflow.
Intent combines related signals, weighs their provenance, and proposes the requirement that appears to underlie them.
Candidate requirements stay reviewable until a person approves, edits, or rejects them.
A draft is easier to trust when you can inspect its sources. Intent keeps that trail visible, including disagreements between what a policy says and what the service does.
Intent can distinguish documented intent from implemented behavior and test-enforced expectations.
Intent should not silently reconcile competing statements into a single requirement.
Nothing becomes an approved requirement just because Intent suggested it. Review the draft, make any changes, and publish only what your team stands behind.
Bohmian keeps the richer discovery context: source revisions, provenance, rationale, rejected candidates, and reviewer edits.
Once approved, a contract can be synced into a connected Wyrd deployment for use in verification and evidence collection.
Candidate requirements remain grounded in the connected systems and artifacts that support them.
No inferred requirement becomes authoritative merely because an AI system proposed it.
Bohmian can manage discovery while Wyrd remains the open execution substrate for assurance.
Connect your sources. Review what Intent finds. Decide what should be verified.