# Continuity foundation

Illustrative companion to the customer-quote starting brief.

## Source of truth

Git holds implementation and reviewable documentation. The application's request record holds customer facts, quote revisions and approvals. A task tracker, if used, holds current work status. Assistant memory can retain a short pointer to a confirmed decision; it does not replace these sources.

## Decision record

For each decision, keep:

- What was chosen and which process step it affects.
- Why it was chosen and what cost or limitation it introduces.
- Who confirmed it, when and the supporting source.
- What new evidence would cause it to be reconsidered.

Initial proposal: manual intake before mailbox integration. It makes the first path easier to inspect and test, while retaining manual copy-and-paste work. Owner confirmation is pending.

## Handoff between contributors

Use this short record at a meaningful transition:

```markdown
Goal:
Current implemented slice:
Files / branch / revision:
Verified behaviour and evidence:
Open questions and assumptions:
Known failures or incomplete paths:
Next action:
Owner of that action:
```

The receiver reads the referenced files and checks before relying on the summary. Start with one contributor unless concurrent work has a clear benefit. If several agents are used, give each one a bounded area and a named integration owner.

## Ownership boundaries

- The business owner defines quote policy and approves customer commitments.
- The developer proposes implementation choices and records their tradeoffs.
- A development assistant operates within the brief and records uncertainty.
- The application enforces version-specific approval and records delivery evidence.

## Initial continuation record

Goal: prove a manually entered request can become an approved quote.

Current implemented slice: none. These files illustrate a consultation deliverable; they are not an application.

Evidence: `process.bpmn`, `process.svg`, and `starting-brief.md` express the proposed path. No business validation or implementation tests have been performed.

Open questions: required fields, catalogue authority, roles, external AI data handling and delivery provider.

Next action: confirm the boundary and inspect the intended repository, then implement with synthetic records and a test delivery adapter.

## Memory scope

Retain confirmed project decisions and source pointers. Mark proposals as proposals. Update superseded decisions instead of allowing contradictory versions to circulate. Keep personal/customer content out of general agent memory unless a specific, authorised need exists.

This is a documentation foundation. It does not provision a memory service, agent plugin or orchestration runtime.