SCHEMA
This vault is built on the towers_book record spine. One record type per note; one note per record. The spine is unchanged from the source schema. One extension is declared below.
Record Spine
| Type | Folder | ID key | Function |
|---|---|---|---|
question | 00_Questions/ | question_id | The determination the vault must settle |
map | 00_Maps/ | id | A domain, with the concepts needed to navigate it |
concept | 10_Reference/Concepts/ | id | A term in the corpus's own sense |
person | 10_Reference/People/ | id | A figure cited as authority, counter-voice, or subject |
passage | 20_Passages/ | passage_id | The evidence, quoted; the audit trail to the corpus |
insight | 30_Insights/ | insight_id | One distilled reading of one passage |
system | 40_Systems/ | id | An assembly of the corpus into a working structure |
Every record carries tags and explicit wikilinks, and every record carries status except insight — the spine's insight template omits it deliberately, because an insight's standing is already stated by textual_authority and corroboration, and a separate status field would give a second, competing answer to the same question. No record is orphaned: each passage answers at least one question; each insight cites one passage and one concept; each system lists every passage it draws on.
Passage Fields
The source spine's passage template carries HUMINT attestation fields — attested_date, attested_time, attested_place, subject, attribution. Those are meaningful for an intercept and meaningless for a document, so passage notes here carry citation, locator, quotation_status, textual_authority and corroboration instead. The ID key is passage_id, as the spine specifies. The substitution is recorded because an attestation field left empty and a field replaced look identical to a reader who only sees the result.
Rating Scales
textual_authority — the weight a claim may bear.
A— verbatim, retrievable, primaryB— attested but second-hand, or primary with an unresolved editorial questionC— reconstructed from context; the words are not on the pageD— the corpus asserts it without supportE— contradicted by another part of the corpusF— provenance unknown
corroboration — 1 (independent confirmation) through 6 (no determination possible).
Extensions Declared
One record type sits outside the source spine. It is declared here so that the deviation is auditable rather than silent.
literature — 70_Literature/
Retrieved external research, admitted so that the corpus's claims can be read against what the field actually found. Records use type: "literature", ID key id (LIT-###), and carry:
citation— the register row (CIT-###)identifier— the resolvable identifier, or the literal stringUNVERIFIEDretrieved— the date the primary record was openedbears_on— wikilinks to the operator records the source bears upontextual_authority/corroboration— rated on the same scales as every other record
A literature record is not a passage. It does not quote the discussion, and it is not evidence for what the corpus meant. It is evidence for what the field found, and its bears_on links run one way: literature bears on the operator's claims, never the reverse.
confrontation — 80_Confrontation/
This is the comparison apparatus the second session added, and it is the reason the vault exists in its present form. A confrontation record pairs one operator position with the literature bearing on it and states a verdict. Fields:
operator_position— theSYS-###,MAP-###orINS-###records under testliterature_position— theLIT-###records bearing on itverdict— one ofConverges,Incomplete,Evidence Now Exists,Reversed in Part,Unaddressedtextual_authority/corroboration— rated for the confrontation's own conclusion, not for either side of it
Each confrontation keeps four fixed sections in fixed order: The Operator's Claim → The Literature's Position → Where They Agree → Where They Diverge, followed by What Changes in the Vault. The four-part order is the point: a reader can see the agreement before the divergence, which prevents the record from being read as a refutation when it is a convergence.
Unaddressed is a verdict about the vault, not about the corpus. It means the corpus makes no claim where the literature requires one — a missing position, not a wrong one.
Validator Contract
systemnotes keep the five fixed sections in fixed order: Primitives → Assembly Map → Selection Notes → Open Questions-Tensions → Sources.insighttitles and their H2 headings carry the same declarative sentence.confrontationrecords keep the five sections in order: The Operator's Claim → The Literature's Position → Where They Agree → Where They Diverge → What Changes in the Vault, and averdictfrom the declared enum. A### Retrieval Statussection may be appended immediately before the final section when a source the record depends on was not obtained; the gap is then stated in the record rather than hidden.CNF-008is the only record using this allowance.- Rejected or doubtful material is retained and flagged; it is never deleted.