Shared architecture / personal and professional

Records become memory. Memory stays accountable.

An answer is not a loose piece of generated text. The chosen sources, the derivation, the cited lines and the result stay on one spine.

The path / five explicit stages

From source record to living receipt.

The same sequence powers a calm personal brief and a dense professional finding. Only the interface and the review depth change.

01 / Choose

You select the record.

Only what you authorise for that Space enters its working memory.

02 / Connect

The memory joins related facts.

Names, dates, amounts and changes can be followed across separate sources.

03 / Derive

Inspectable logic computes what it can.

Calculations use explicit inputs. Written summaries stay tied to source quotations.

04 / Challenge

Every cited quotation is re-checked.

Each quotation is compared with its source before it is shown to you.

05 / Receipt

The result keeps its working record.

Sources, quotations, inputs and outcome stay inspectable together.

Stage 04 verifies that a quotation exists in the source it cites. It is not independent legal or factual verification of the conclusion.

Why cross-document memory matters

The useful answer often lives in no file.

A payment term in a contract, a total on an invoice and an acceptance date in a message produce a due date that none of those records states on its own.

Source record

[01]contract.txt
50% + 30 days
[02]invoice.txt
$4,800 total
[03]acceptance.eml
Aug 16 acceptance

Derived answer / inputs attached

$2,400 due September 15.

3source records
3exact quotations
When the record does not support an answer, the pipeline returns the gap instead of filling it.

Receipt anatomy

Enough detail to inspect the computation.

A receipt is more than a footnote under an answer. It records what was authorised, used, calculated, cited and challenged.

Scope

The Space and source set authorised for the question.

01
Source identity

References and hashes for the records used.

02
Derivation

The inputs and the rule behind the result.

03
Exact quotations

The lines that support each factual claim.

04
Challenge result

Whether each cited quotation matched its source.

05
Outcome class

Derived answer, explicit conflict, or insufficient evidence.

06

One architecture / two products

Use it for continuity. Or use it for defensibility.

The standard stays the same: exact sources, inspectable computation, visible conflicts, and an honest stop when evidence is missing.