Ascribe OES 1: a person, described without a name
Ascribe is the MiniCOSM for a person's holograph
Outline
- Contents — Contents, in Ascribe OES 1: a person, described without a name
- How to read this — Must is a rule a conforming reader or writer keeps
- 1 Provenance and the name — where Ascribe comes from, and what the name says
- 2 The model on one page — a folder that is the self, ten containers of nodes, and the forms they anchor to
- 3 The design rules — seven rules every part of Ascribe answers to
- 4 The holograph — the folder, its catalog, its module files, its ids and paths
- 4.1 The volume — A holograph is a folder, laid out as a Holotype's atoms are
- 4.2 The catalog — A catalog never holds the person's name, an email address, a phone number
- 4.3 Ids and paths — Inside its own volume an id is written bare
- 4.4 An example — A holograph small enough to be one file, every node in the catalog
- 5 The ten containers and the forms — ten kinds of node, one per module, and the forms they anchor to
- 5.1 The containers — Each container holds one kind, named for the singular of the module
- 5.2 The forms — Module F, Forms, holds the things a self is about and how they combine
- 6 The envelope — Comprise's envelope plus six fields of Ascribe's own
- 7 Links and relations — a starter list of relations, and the ones an author declares
- 8 The dialectic — the opening questions a guided process asks, four for each module
- 9 Checks — MacroCOSM's generic checks, and six of Ascribe's own
- 9.1 The generic checks — The manifest selects load and the envelope checks duplicate-id, id-grammar, id-module, type, type-prefix, identity-min, provenance
- 9.2 Ascribe's own — Run by enough/ascribe.py (lint_holograph) after the generic ones, in one report
- 9.3 What reads like personal data — no-pii reads every string of the catalog and of every item, every key
- 10 The private filter — what ingest and transfer leave out of a holograph
- 11 The command line — one command that checks a holograph folder
- 12 Projections, by reference — what leaves a holograph, and how; built in Thym, not here
- 13 What is not built — what 0.5.0 leaves for later rounds
- 14 Decisions in this version — the rulings and readings Ascribe OES 1 settled, one line each
- Colophon — Written 2026-11-02 for enough 0.5.0, version 1 of Ascribe OES
Glossary
- a company (Comprise)
- a company (Comprise), called holotype in the files — defined in How to read this
- a person (Ascribe)
- a person (Ascribe), called holograph in the files — defined in How to read this
- Ascribe-Connect
- the service that would vouch that one real person holds a holograph — defined in §13 What is not built
- The application module
- the process that asks the dialectic's questions and writes nodes — defined in §13 What is not built
- The private filter's code
- the rule is declared (section 10) and nothing applies it — defined in §13 What is not built