Implemented foundations
Local product and signed exchange contract
On-box ingestion, Audit and Ask; engineer adjudication; enrolled identities; signed revision envelopes; scoped visibility; durable local storage; replay and conflict handling.
Site architecture
Every box works locally. The site remains one governed environment.
Cortessa is being developed around a simple boundary: analysis stays with the engineer; approved revisions can move through an offline, permission-scoped site network; authority stays with people.
01 / TopologyInside the air-gapped site boundary
Engineer boxes → departmental nodes → on-site hub
The target architecture does not send prompts, documents or model inference to an external service. It joins self-sufficient engineer boxes through governed internal nodes, while keeping department scope and human ownership explicit.
-
Engineer boxes
- Local documents
- Local ingestion and model
- Audit · Ask
- Engineer approval
-
Departmental nodes
- Enrolled scope
- Signed revision exchange
- Department-default access
-
On-site hub
- Permitted aggregation
- Selected cross-department sharing
- No central approval
02 / Engineer boxSelf-sufficient local operation
The engineer does not depend on the network to think
- Local corpus. The box holds the engineer's approved documents and working context.
- Local pipeline. Extraction, cleaning, chunking and indexing run on-box.
- Local model. Audit and Ask operate without sending the corpus or query outside the box.
- Human authority. Cortessa surfaces and cites. The engineer adjudicates and approves.
03 / Governed revisionThe evidence travels with the decision
An approved revision moves. An AI answer does not become site truth.
Audit surfaces a candidate
The engineer inspects the cited source and records a disposition.
The engineer approves
The revision is bound to its owner, content digest, lineage and sharing scope.
The department carries it
The signed revision can move through enrolled nodes within its permitted scope.
The receiver reviews it
Receipt does not silently certify, supersede or add content to another engineer's searchable corpus.
04 / AuthorityNo automatic winner
The network preserves disagreement instead of hiding it
The hub can aggregate only its enrolled scope. It cannot publish an engineer's approval, choose a winning branch by arrival time, invent missing ancestry or erase an existing conflict. Gaps and competing heads remain visible for authorised people to resolve.
05 / MaturityWhat exists · what remains
The product and the target architecture are not being conflated
In development
Production site networking and rollout
Authenticated peer transport, key provisioning and recovery, delivery scheduling, backup and restore, migration, controlled corpus promotion and real-site deployment.
Not claimed
No deployed-network or DMS-replacement claim
Cortessa is not presented as accredited, production-deployed, automatically synchronised or already replacing every document- and records-management function.
Start with evidence. Design the site route from there.
A bounded evaluation proves the local Audit and Ask workflow first. The next stage defines the departmental authority, revision path and security boundary needed for a site deployment.