Status: Constitutional Phase 11 architecture freeze
Scope: Uromarisi-attributed historical activity semantics, Phases 1-10
Admission: Private research_only data and computation
Public-data default: Forbidden
The subsystem governs one bounded historical-text corpus of activity-position
records. Its primary identity is (activity, ordinal, verse). The corpus is
not a clock, a birth identity system, a relationship table, a condition score,
or a prognostic engine.
The source authority is the hash-bound Uromarisi research fixture chain. It governs only the bounded transcription and editorial decisions named in those fixtures. It does not establish a universal Pancha Pakshi canon, medical truth, or cross-witness equivalence.
The executable layer order is fixed:
A later layer may project only facts already explicit in an earlier layer. It may not use its abstraction to invent earlier source or doctrinal truth.
The closed materialized corpus contains 24 unique cells in canonical activity order: EAT, WALK, RULE, SLEEP, DIE, preserving source ordinal order within each activity. SLEEP ordinal 5 is absent. Verse 250 is an explicit identity conflict and remains outside every materialized corpus.
Every classification, relation record, local profile, network node, and
hardening receipt must preserve the same activity, ordinal, verse, source
decision identity, and source digest. Containers are immutable tuples. Missing
lookups return None; they never select a neighbor or synthesize a record.
The sole Uromarisi classification policy is
moira_explicit_uromarisi_activity_ordinal_lookup_research_v1. Activity and
ordinal are explicit caller inputs. There is no default and no admitted
temporal selector binding.
The separately recorded Bogamuni weighted-Sookshma and equal-fifths selector policies are not Uromarisi source truth. They cannot be attached to this corpus without a new, explicit cross-witness composition decision.
Seventeen cells contain a detected relation clause and seven explicitly do not
record one. Detection is not semantic admission. Ten detected clauses remain
unresolved_clause; seven retain only their exact named surface category.
No bounded record establishes a relation endpoint or direction. Consequently:
Surface words may not be normalized into friendship, enmity, direction, reciprocity, weights, loops, or endpoints.
Each local condition is the exact structural join of one classification and
one relation record under the explicit policy. All 24 profiles have status
not_evaluable_no_admitted_condition_doctrine. Favorability is not assigned,
condition score is None, prognosis is not performed, and medical use is
forbidden.
The Phase 8 aggregate contains structural counts only: 24 profiles; activity
counts 5, 5, 5, 4, 5; 17 detected and 7 not-recorded relation clauses; 10
unresolved and 7 named-surface clauses; zero admitted and zero scored
relations; and blocked verse tuple (250,). Counts are not ranks, weights,
judgments, or evidence of effect.
Phase 9 projects all 24 profiles into canonical nodes. Its 17 relation candidates are annotations owned by the node whose source record contains the detected clause. A candidate is not an edge.
The node identifier format is <activity>:<ordinal>:verse:<verse>. Node and
candidate order follows the earlier canonical corpus. Candidate source binding
is identical to its owning profile and relation record. Endpoint inference,
direction inference, duplicate-edge collapse, self-loop repair, and conflict
repair are forbidden.
Phase 10 freezes a deterministic structural fingerprint over policy identity, node identities, source bindings, classifications, semantic markers, uncertainty counts, relation surface state, evaluation state, candidate ownership, empty edge sets, blocked conflicts, and metric availability.
The canonical Phase 10 structural SHA-256 is
2133ad1c72ea5209facbb83ff8f40cfd09c1efea5340df7943fe08ff599cface.
Its value is regression evidence for this exact bounded structure, not an
external authority validation.
The subsystem fails closed. It rejects:
No fallback, implicit policy, ambient state, network download, or kernel is part of this research path.
The modules _pancha_pakshi_classification, _pancha_pakshi_relations,
_pancha_pakshi_condition, _pancha_pakshi_aggregate,
_pancha_pakshi_network, and _pancha_pakshi_hardening are private. Their
historical records, profiles, aggregates, networks, fixtures, and materializers
are not package exports, facade products, manifest capabilities, or REST
contracts.
The only Phase 12-eligible public product is immutable constitutional status:
that Phases 1-12 are complete, the Uromarisi data remains research_only, the
network remains private and non-evaluative, relation semantics and topology
are not admitted, medical use is forbidden, and no research data is returned.
This governance product may be exposed at package and facade level. It must not
be represented as a runtime profile or REST computation.
Validation uses the project .venv, strict known-issue expiry, test mode, and
no network. The evidence classes are:
This subsystem has no external numerical-oracle claim. It performs no astronomical calculation and exercises no native path or planetary kernel. Fixture hashes prove bounded repository identity, not doctrinal truth outside the named witnesses.
This standard does not claim translation authority, independent textual
lineage, universal doctrine, temporal-selector attribution, relationship
meaning, condition evaluation, favorability, scoring, prediction, diagnosis,
medical validity, or corroborated_public admission. Commissionerate A5 is not
required for this private closure or its governance-status surface; it remains
relevant only to a future stronger corroboration claim.