David/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

session 2026-06-06: Seb reply arc (3 notes) + mindfabric-00 root-cause + PENDING-27 + Basic Memory trial memory

Browse Source
This commit is contained in:
David F Glidden
2026-06-06 12:51:35 +02:00
parent 3f9a89b00c
commit 14e14826c8
7 changed files with 133 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PENDING.md
+10
View File
@@ -790,3 +790,13 @@ The Jurist's six-phase authorization map governs sequencing. Cross-cutting succe
**Recommendation:** Option 1 — the role-(b) choice (new class vs unification) is a genuine taxonomy question the jurist should rule on; unification is the leaner answer but touches the qualifier-mark grammar (§V).
**Files affected:** ~11 templates, 100+ content files, `_utilities.scss` + `_layout.scss` (the holding rules), apparatus-spec + Selector Index cross-references.
**Awaiting:** Steward authorization + jurist name-lock. Until then the holding value stands; no migration work proceeds.
## PENDING-27 — Steward-instance telemetry export contract
**Date:** 2026-06-06
**Tag:** PROPOSAL
**Summary:** Establish the standing contract under which derived statistics may leave a steward's production CapableMind instance: content-free by construction · operator-initiated, never pollable · bounded purpose · steward-reviewed before transfer.
**Rationale:** Seb's B1.3 proposal (b1.3-causal-floor-instrumentation-2026-06-02) asks for a base-score histogram from mindfabric-00 — the first extraction of derived statistics from a steward's production instance to inform engineering. The class will recur (fleet telemetry, A2 baselines on real instances, future calibration asks). The privacy analysis (2026-06-06, Tier B note §5) found that even content-free aggregates leak through two channels: totals proxy ingest volume, and any pollable surface turns deltas into a time series of the steward's activity intensity. The adjacent finding — the full /health payload (incl. `idle` presence transitions, `budget`, per-module cursors) served unauthenticated on a VPN-reachable bind — shows what improvisation produces. This is the inward-facing analog of the ARC AI-posture ruling (REVIEWED pending, 2026-06-05): what may be made of the substrate is the steward's to grant, per purpose, not a default. Constitutional-adjacent because it is a consent rule about the steward's own cognition substrate; jurist read requested.
**Options:** (1) Adopt the four-clause contract above as a standing rule recorded in the L1 governance docs; each future request cites it and names its bounded purpose. (2) Rule per-request with no standing contract (status quo — improvisation each time). (3) Defer to L2 formalization (the privacy-tier vocabulary exists in spec but L2 is parked through May).
**Recommendation:** Option 1. The contract is small, the case in hand is easy, and the fourth request should inherit a rule, not a negotiation. Drafted operationally in the Tier B note §5 (cm-ctl distribution-export as v1 mechanism, replacing the pollable /health field); the PENDING item is the *standing* rule, distinct from the B1.3 instance.
**Files affected:** `~/_Dev/CapableMind-AI/docs/thinking/David/l1-reliability/cover-note-seb-tier-b-2026-06-06.md` (operational half, sent to Seb); a governance doc home for the contract TBD on authorization (likely `docs/thinking/David/methodology/` or l1-reliability).
**Awaiting:** Steward authorization + jurist review (constitutional-adjacent: consent rule over steward substrate).