5 Commits

Include renames

Author	SHA1	Message	Date
mathiasandClaude Sonnet 5	1cea2c9f78	feat(capture): remove summary->ai-sessions write path ... ai-sessions#13: capture's `summary` field wrote a frontmatter shape (title/harness/fidelity/captured_at/repos_touched) that ai-sessions' own extract/audit pipeline can't parse -- silently invisible to that repo's own audit tooling, and bypassing its redaction + Stage2 completeness gates by construction. Only 5 files ever landed this way over 3 weeks; the summary capability's whole value (speed) fights ai-sessions' whole value (redacted, audited, complete), so kill it rather than build a second parse branch. capture now persists insights -> brain and action items -> Gitea tickets only. Removes Summary/SummaryResult/SummaryWriter and all wiring (service, REST body, MCP tool schema); close-session updated to stop assembling a summary payload. specs/capture-*.md kept as historical record with a superseded note -- the feature shipped and is documented, just no longer current behaviour. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WPdSHbp9Utb2hPFm9wDG59	2026-07-27 23:17:56 +02:00
mathiasandClaude Opus 4.8	98cfae595c	feat(classification): data-sensitivity taxonomy + per-wing/repo tags (#50) ... Implements the I1-prerequisite from #49/#50: the classification taxonomy and the per-wing / per-repo tagging the capture server reads to derive a target's sensitivity. - Levels public < internal < confidential, ordered so "stricter wins" (spec §4.1 model C) is a plain max via Stricter(). - Tags read from an optional classification.yaml at the brain root (wings:/repos: maps). Absent file → defaults-only, not an error. - Defaulting: client-* → confidential; hyperguild/homelab → internal; everything else → confidential. Fail-safe-to-strictest is the load-bearing property: a missing tag never silently downgrades. - Config.Derive(Target) is the function the use-case calls; Wing/Repo are the per-kind helpers. ParseLevel rejects unknown tokens; a bad level in the config file is a hard load error. Central classification.yaml (not _index.md frontmatter, not gitea repo topics): classifying a repo needs no live Gitea client, so #50 has no dependency on the tracker work (#52); it's auditable in one place; and it avoids BuildWingIndex clobbering a wing's regenerated _index.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-06-22 22:42:05 +02:00
mathias	2a595b5a92	docs(capture): make Q4 audit-sink-down posture classification-aware (#49) ... Reconsidered Q4: instead of one global degrade-and-warn, the posture now inherits from effective classification (Q1): - confidential + audit-sink-down -> hard-refuse (no buffer; removes the buffer-integrity question for confidential data) - internal/public + audit-sink-down -> degrade-and-warn + durable local buffer + ntfy + reconcile-on-recovery - floor (all tiers): refuse if nothing can record the audit Updated the I5 Gherkin scenarios + obligations row to match. Couples Q4 to the Q1 classification spine -> one coherent sensitivity model.	2026-06-22 20:20:40 +00:00
mathias	b7a2cc5fdf	docs(capture): resolve §4 open questions into binding decisions (#49) ... Q1 classification trust: model (C) — caller declares, server cross-checks target tag, stricter wins, mismatch logged. Needs a classification taxonomy + per-wing/repo tags (prerequisite, sub-task of #49). Q2 harness origin: server-derived from authenticated principal; context.harness is descriptive-only, never a gate input. Q3 central relay: ships in v1 (needed for claude.ai/Crush/Pi/LLM Council) + I2 security-baseline ledger entry is v1 work. Q4 audit-sink-down: degrade-and-warn + durable local buffer + reconcile on recovery; refuse only if NOTHING can record the audit. Updated the I1 sovereignty + I5 auditability Gherkin scenarios to match; added classification-mismatch and origin-spoofing scenarios.	2026-06-22 20:17:07 +00:00
mathias	db638cca11	docs(capture): add use-case + BDD spec for the capture capability (#49) ... Pre-build spec for the uniform cross-harness capture path. Grounds the design in the homelab invariants (I1-I5, now canonical on infra main): - I1 sovereignty gate: refuse confidential capture via us-nexus harness - I2: distributed-library form (no high-degree observer node) is admissible; central relay needs a security-baseline ledger entry - I5: capture is a privileged write path, must emit audit records Gherkin scenarios cover the happy path, the sovereignty refusal, supersession + staleness discipline (#45/#47), fail-closed validation, best-effort partial-failure receipts, dry-run, and fidelity supersession. Four open questions flagged for review (classification trust is the highest-risk one).	2026-06-22 17:25:03 +00:00