Contracts

A contract is a unit of work in Quangence: it groups context, agent activity, and outputs for a specific effort (for example a feature, investigation, or migration). It is the durable anchor so decisions and artifacts do not get lost in a single long chat.

What you use contracts for

• Traceability — See what was decided and what was produced for a given effort.
• Handoff — Give the next person (or future you) a clear place to start.
• Scope — Separate one initiative from another instead of mixing everything in one thread.

What you will see

Open Contracts from the app sidebar to browse the list. Selecting a contract opens its detail view. The exact panels and labels depend on product version and how far that contract has progressed, but you can expect areas for summary, activity, and artifacts (or equivalents) over time.

Screenshot placeholder — Contracts list (table or cards: title, status, last updated). Match your actual UI.

View contracts

• Use sorting or filters if your build exposes them to find active or recent work.
• Open a row to see full detail: conversation-linked context, steps taken, and downloadable or copyable outputs where available.
• If something looks stale, refresh the view or navigate away and back; real-time updates depend on deployment.

Screenshot placeholder — Single contract detail: header, tabs or sections, and key actions.

Relationship to the workspace

The workspace is where live interaction happens; contracts are where structured, effort-scoped records accumulate. You can move between them as your workflow needs—start in the workspace, then file or open a contract when the work deserves its own home.

Next steps

• GitHub if your contract work touches repositories.
• FAQ for limits, support, and data questions.