Dashboard › institutional-transition-lab › Distillation
Distillation
ID: 5ceae0c1-e8aa-4d7e-adfd-9dd62c85071f
Generation: 0
Tokens: 930
R_compression: 15.031
C_norm: 0.000
Archived: No
Created: 2026-09-08 20:55:51
Source IDs:
["lore_tm_v1_q111l0UhD9uaMkcRL6DDiS49Q1kBt2GLX9IbTEGwnGU"]
Observations
- 🔴 (20:44) User directed that governance records must always be adjudicated research-only from specified frozen inputs, with hashes and provenance verified before analysis.
- 🔴 (20:44) User requires a source-first, performance-blinded workflow: inspect only the authorized protocol, schema, frozen source material, and permitted coding package, in the user-specified order; independently review complete primary-source bodies, metadata, and patches before consulting model codings or summaries.
- 🔴 (20:44) User directed never to inspect performance outcomes, detector output, transition dates, or unrelated reports during governance adjudication.
- 🔴 (20:44) User directed never to edit files or perform git mutations during governance adjudication and related repository research.
- 🔴 (20:44) User requires every institutional field and power edge to be grounded in exact verbatim
quote/source_id evidence pairs, with source provenance and explicit evidence limitations.
- 🔴 (20:44) User requires proposals, announcements, and effective changes to remain distinct, including announced dates versus effective dates; unsupported conclusions must result in abstention rather than inference.
- 🔴 (20:44) User requires complete requested artifacts or substantive research findings and never permits empty output; when blocked, the response must identify the exact tool or error blocker.
- 🔴 (20:44) User requires canonicalization to remain closed while unresolved, OpenCode-hosted OpenAI review to be labeled LLM-assisted rather than human, and Gemini 3.7 Flash to be used only for triage.
- 🟡 (20:44) Project methodology in
/home/byk/Code/institutional-transition-lab/.lore.md uses the forecasting chain power-graph change → behavior/culture → delivery capability → market or ecosystem performance, chosen over an after-the-fact inclusivity score because the project tests prediction and mechanisms rather than narrative fit. Performance transitions and institutional histories remain independently produced until frozen; prescriptive advice is reserved for mediator, intervention, and prospective-validation stages.
- 🟡 (20:44) Project methodology represents institutional events as versioned power-graph diffs rather than leader-title or narrative labels. Nodes are actors or bodies; scoped edges represent rights such as
appoint, remove, fund, approve, merge, or veto; transfers use paired removal/addition unless the same actor retains a modified right; announced changes remain distinct from effective changes.
- 🟡 (20:44) The separate closed
governance-adjudication-v1 schema was chosen instead of extending the hash-pinned coding schema because modifying frozen bytes would break reproducibility. Decision semantics are: accept adopts one valid frozen response exactly; revise records a supported institutional claim when none is exactly adoptable; reject preserves a resolved non-institutional classification; abstain is only for source insufficiency. The schema requires frozen pins, reviewer/assistance provenance, field-scoped evidence, grounded final coding, and derived validation status.
- 🟡 (20:44) Governance semantic-validation rule: schema validity and reproducible quotations alone do not make a frozen response admissible. Proposals are not institutional events; meeting notes do not prove product implementation; merge metadata proves enactment only for merged rights wording. Direct evidence must support every adjudicated field, because generic hash-pinned evidence or grounded
power_changes alone do not establish class, kind, dates, scope, body/patch relation, title, or completeness.
- 🟡 (20:44) Power-rights interpretation rule: software wording such as “owns,” “responsible for,” or component “maintainer” is treated as an implementation boundary unless the source explicitly grants institutional decision rights such as approve, merge, appoint, veto, budget, or strategy authority.
- 🟡 (20:44) SPDX interpretation rule: adding an SPDX license identifier or copyright notice is treated as attribution or repository control, not an institutional licensing edge, unless the source explicitly changes license terms, licensing authority, ownership, or another institutional right; normalizing a file header alone does not change the power graph.
- 🟡 (20:44) Repository file-style rule in
.lore.md: place the applicable license or copyright block at the beginning of every file, before documentation comments, module descriptions, or other content; preserve the repository’s exact standardized wording and SPDX identifier; where both legacy and Valkey license blocks apply, retain the required blocks with licensing ahead of documentation.