The Architectural Reference

The systems, records, and connections that support human stewardship.

The Guidelines state responsibilities. The Operating Reference follows the person's purpose. This architectural reference connects those responsibilities to source identity, ownership, permission, publication, correction, and continuity.

From a responsibility to a mechanism#

A useful architectural account starts with a human need: recognize the edition, understand an invitation, recover a saved draft, or correct an error. It then names the responsible system, the permitted action, the supporting record, and what happens when the action fails.

Source, edition, and public presentation#

A source is an authored record. An edition identifies a selected version for a particular use. A public presentation makes that edition readable in a place.

Humansteward.org is a public reading presentation. The original Guidelines documents remain separate from the explanatory practice and architecture text. Each included document has a fixed source-snapshot URL and a plain-text download. The source snapshot is identified by a digest of its exact text bytes.

The stable reading address selects the current edition. A fixed edition address identifies the particular text. A new source text produces a new identifier; it must not silently reuse an old text identity. The edition index and source context make those relationships inspectable.

Presentation can evolve without changing the source wording. Build and deployment records identify those changes separately. A source snapshot identifies text, not a new ratification or a guarantee that every product follows it.

Human Stewardship framework#

The repository framework organizes stewardship into volumes, doctrines, principles, implementation guidance, validation, and product applications. Source documents describe append-only volume extension, protected ratified principle wording, product applicability, and validation rules.

Read the preserved framework source and registry source for their exact wording. Those documents identify the implementation they describe. Their source claims should be read alongside current runtime evidence; publishing a source document does not verify a complete deployed object graph.

Current repository direction places realm logic in Java and realm-owned Postgres, with TypeScript at the edge. This site is a static public presentation. It does not create a new realm database, approval authority, or parallel stewardship register.

Ownership and permission#

An architectural boundary should identify the owner of a record and the API through which other systems may use it. A public reading projection can display permitted material without becoming the authority that approves or amends it.

Access, authorship, contribution, ownership, approval, and publication remain separate relationships. A link establishes a path; it does not grant unrelated permission. Reading these references or downloading an edition does not record agreement with them or adoption of the Steward's Oath.

Private work requires access enforcement over the document and its supporting downloads, images, and metadata. An unlisted address or a search-engine instruction is not that enforcement.

Publication and correction#

The publication sequence is draft, prepared review, approval of an exact edition, deployment, and verification of what the public receives. A receipt for one stage does not stand in for the next.

The existing Publishing Desk owns its publication operations. This website's source import and static build create the public reading projection; they do not introduce a second approval database. The current release publishes preserved public sources and the commissioned website explanations. It does not claim that the Publishing Desk has gained a reference-document editing workflow.

A correction needs the affected edition, section, wording, proposed change, and any supporting source. The correction preparation page helps a reader retain that information. Preparing a correction does not submit it, amend a source, or create a publication receipt.

Withdrawal changes what is available. The resulting record should still explain the former identity and the scope of the withdrawal where disclosure is permitted. A rollback restores an identified release; it should retain why that release was selected.

Reading and return on this site#

Complete reference text is delivered in the initial HTML. Headings and contents links allow a reader to move through the work without JavaScript. Each heading has an addressable anchor. Downloads preserve the selected text bytes; print styles present readable text on a light page.

JavaScript enhances navigation, link copying, sharing, local search, and correction preparation. Search runs against the public text in the search page. The application does not send typed search phrases to a separate search service or create a personal reading account.

An edition or section link is the return point. This site does not promise automatic restoration of a reader's scroll position across devices. A browser may provide its own history or bookmarking behavior.

Host, route, and preview identity#

The publication's canonical host is humansteward.org. Initial-response metadata identifies the page and the selected portrait. Image metadata must describe its actual bytes and dimensions. A preview client's rendering and cache remain separate from a successful metadata response.

Existing PosterityOS services and Reader routes retain their own identity. Links between the reference and those places express their relationship. They do not make unlike pages equivalent or transfer private context.

Unknown paths should return a useful page with an actual not-found status. Current-edition redirects should remain temporary so a future edition can be selected without permanently caching the old choice.

Evidence and unresolved source differences#

The source collection contains different statements about ratification across the Guidelines, overview, volume indexes, and Oath. The preserved texts retain those differences. Their status should not be resolved merely by choosing a newer-looking label.

The validation source also refers to six guarantees alongside seven named checks. A limited source guard does not establish universal AI behavior enforcement. Those differences remain matters for source reconciliation, not silent editorial repair in this website.

For any architecture claim, retain origin, date, scope, and method. Distinguish documented intent, implementation in source, observed behavior, and an unresolved gap. Formal acceptance and register reconciliation follow the responsible review process; a successful build alone does not establish either.