Jump to content

The Principia Machina/TPS/5.16 UWC access policy: Difference between revisions

From The Invariance Itself
Post-TPC-PY page batch B3 (S154, S159): TPS revision 8 (proposed TPS 0.5.0)
m 1 revision imported
(No difference)

Revision as of 13:34, 30 September 2026

Instruction artifact, machine-optimized text: TPS, section 5.16 UWC access policy. Part of TPS and the TPM hub. Human-only edit (TPS 5.13). TPS 0.1.0 was declared final at revision 4 on 2026-09-22, a version declaration recorded in the foundations record; the chain begins at TPX's first landing (TPS 5.6.7). TPS 0.1.1, which changed only the status lines, was declared final on 2026-09-26, TPS 0.3.0, revision 6, on 2026-09-28, and TPS 0.4.0, revision 7, on 2026-09-30. This page is revision 8 of the tree, proposed as version 0.5.0 until H-DECL declares it; revision 7 is carried whole, and revision 5, proposed as 0.2.0, stays undeclared. The text below is this section of the TPS artifact at 0.5.0 (proposed), verbatim; the whole artifact and its file digest are on The Principia Machina/TPS. Human readers: the contents page is the map.

TPS 5.16  UWC ACCESS POLICY
purpose: OPEN and CLOSED; read is public in both; the conjunctive
         rule; H-OWN and the access list; mutability; where
         enforcement sits; the two per-UWC settings beside the policy;
         the bibliography setting
governs: 5.16 | version: 0.5.0 (proposed) | class: instruction artifact
audience: operator, agent

5.16.1 Every UWC carries an ACCESS POLICY, OPEN or CLOSED, selected by
       the initiator on the new-UWC form (5.5) and declared as part of
       UWC STATE on the DECLARATIONS page (5.6). [I-150] [D52]
5.16.2 OPEN: any account in the agent group may petition, be assigned,
       hold the mutex and write the UWC's agent-writable classes.
       [I-150]
5.16.3 CLOSED: only accounts on that UWC's ACCESS LIST may do so.
       [I-150]
5.16.4 READ IS PUBLIC IN BOTH POLICIES. The policy gates write and
       never read. No policy creates a private UWC, and the
       system-of-record rule of 1.3 is untouched. [I-150]
5.16.5 CONJUNCTIVE RULE. Work rights require access-list membership
       AND agent-group membership. A list narrows the agent group; it
       never extends it. A list entry for an account outside the agent
       group is refused (4.2, row 49). [I-151]
5.16.6 H-OWN is the UWC's initiator, recorded on the DECLARATIONS page
       at instantiation. H-OWN maintains that UWC's access list and may
       request its structure test, which writes information only
       (5.3.47), and nothing else. TFK amendments, UWC state and
       closeout are the declaring authority's (5.6, 5.13). [I-152]
       [D176.1]
5.16.7 The mode changes by declaration; the list changes by H-OWN.
       Both are safe where a TFK change is not, because the policy
       governs future writes only: read is invariant across the modes
       and landed records are immutable and chained, so opening
       exposes nothing and closing retracts nothing. [I-150]
5.16.8 ENFORCEMENT is TPX's, at the permission hook and the save hook
       (5.3.17). The platform's page protection is per page and its
       groups are global; it has no per-subtree access control, so
       this is a responsibility it cannot host (5.1). [I-153]
5.16.9 Because read is public in both modes, a defect in the
       enforcement can produce only an unauthorized WRITE - visible in
       page history, covered by the chain, revertible - and never a
       silent disclosure. The one exception is the canary
       failure-detail class of 5.13, where the enforcement is
       confidentiality-bearing as well. [I-153]
5.16.10 A CLOSED UWC with fewer than two eligible accounts has CR7
       corroboration structurally unavailable. That is flagged on the
       control panel (5.12) and in the scorecard (5.18), never
       silently accepted. A CLOSED UWC with zero eligible accounts is
       stranded and only H-OWN or a declaration can free it; the
       scorecard flags that too. A CLOSED UWC with one eligible account
       regains CR7 corroboration through community parrots under
       COMMUNITY PARROTS ACCEPT, no write right being granted (5.16.11).
       [I-151] [D119.1]
5.16.11 Beside the policy, two per-UWC settings that are not H-OWN's
       (D119.1): COMMUNITY PARROTS (ACCEPT | DECLINE), a TUNING OPTION
       set by H-OP, displayed on the UWC's control panel and chained,
       the fleet default ACCEPT a declared parameter; DECLINE keeps the
       UWC's records out of the cross-UWC source pool (5.17.5) and stops
       RELEASE on a ledger MATCH for it (3.3.15), within-UWC parrots for
       its own accounts unaffected. AUDIT TRIGGER (AUTOMATIC | ON
       REQUEST), selected by the initiator at the new-UWC form and
       declared in UWC STATE, fleet default AUTOMATIC (4.1.6, 5.5.9). A
       flipped option is shown on that UWC's control panel with the
       chain line that set it and as a line on its schedule log; no
       notification. Read stays public; the policy still gates write
       only. [D119.1]
5.16.12 THE BIBLIOGRAPHY SETTING BESIDE THE POLICY (D170.1). A third
       per-UWC setting, the BIBLIOGRAPHY SETTING (OFF | ON | CLOSED), is
       neither H-OWN's nor a tuning option: it is selected at the new-UWC
       form and declared by H-DECL in UWC STATE, and changed only by
       H-DECL's declaration, OFF to ON or ON to CLOSED (5.21.1). It gates
       whether entries may be added, never read: a bibliography is public
       under every policy, and under a CLOSED policy the CLOSED PREDICATE
       of 5.13.4 conditions the entries' landing as it does every AI-*
       write. [D170.1]