Engineering documents published as pages rather than PDFs, so they can be linked to a line, read on a phone, and corrected without reissuing a file. The library is new — these are the first entries, and the conventions below are what the next one should follow.
Specifications
One case, two schemas: where the write and read models diverge, how custom fields arrive from the form template, the two storage philosophies connectors have chosen, and the mappings that have no clean answer yet.
DRAFT TSANET-2026-002The platform brokers file transfer and never stores it. What that forces on the connector, why delivery reaches both parties, and the two responsibilities the platform leaves entirely to you.
DRAFTArchitecture & assessment
Not numbered, because they describe a specific connector rather than specifying platform-wide behaviour — but they belong to the same library and are written to the same standard.
Why a hosted gateway rather than an installed app, the runtime as built, and the submit-outcome taxonomy that parks ambiguous submits for reconciliation rather than retrying them into duplicates.
Architecture CONNECTORZAF sandbox constraints, ZIS integration naming, the three-audience note visibility model, and the API-token retirement clock.
Architecture PLATFORMA pre-implementation map with every claim tagged by evidence level — surfaces, Table API traps, and the distribution choice certification gates.
AssessmentAuthoring
Copy the template, keep the section numbering, and change nothing about the styling.
Duplicate tsanet-design-doc-template.html and rename it tsanet-2026-NNN-short-slug.html. It links hub.css and doc.css and defines no colours of its own — leave it that way, so a brand change lands everywhere at once.
The Verified against cell is the one that matters: name what you actually checked. "The OpenAPI specification" and "a live call on Beta" are useful; "internal knowledge" means the reader should not trust the numbers.
Note for a convention worth pulling out of the flow, Constraint for something that will bite. Not for emphasis in general — a page where everything is highlighted highlights nothing.
Inline SVG using .bx, .ln, .tt, .ts, .tl from hub.css rather than literal colours. Give each figure a caption that says what to take from it, not what it depicts.
Conventions
| Convention | Detail |
|---|---|
| Document number | TSANET-YYYY-NNN, allocated in sequence within the year. The number never changes, including when the document is superseded. |
| Status | DRAFT while it can still move, APPROVED once ratified, SUPERSEDED when a later document replaces it. A superseded document stays published and links forward. |
| Version | Independent of status. Bump it for any substantive change and add a revision-history row saying what moved. |
| Cross-references | By number and hyperlink. Every document in this library is a page, so a reference that does not link is a reference the reader has to hunt for. |