Digital Assetsda.fimpo.net
Admin PIN
← Back·All grounding·Dashboard·SPEC

Spec — product contract

What the live app is responsible for (PROMPT_VERSION=trust-v8).

Surfaces

Surface Purpose
Dashboard / Sticky Focus (severity) · within-focus Action · Intelligence · Cards (Source/Chain filters live inside Approval chains)
Admin /admin Scan, routing, snapshots, benchmarks (admin-only), reference links
Grounding /grounding Curated docs (Trust · Why · Methods · Spec) — viewers; bake-off docs admin-only
Data volume /app/data cards.json, cache, detection, org snapshot, deep corpus (proposals/issues/workflows/deep_scan/corpus_index)

Rules

  1. Comments from the issues endpoint; assert ≥95% coverage.
  2. Cited grounding only — authority is TRUST_GROUNDING.md; runtime table cited_facts.py.
  3. Trust rules sit at the top of every classify prompt (confidence tags carried into responses).
  4. Attribution evidence-only — DA ≠ Foundation; no invented institutions from handles.
  5. Project 3 = Incoming; Project 5 = Milestones (both labeled).
  6. Proposal content = /proposals/*.md (not PR body checklist).
  7. Severity = single resolve pass (highest wins), including architectural invariant overrides (violated→critical, at_risk→≥watch).
  8. Every action card shows collapsible Sources; Intelligence cards show Sources + Citing. Cards also show invariants (privacy / authorization / composability) and optional trade_off on watch/critical.
  9. Hide empty sections rather than hollow cards.
  10. DA self-funding share from proposal filenames is a first-class dashboard insight.
  11. Architectural integrity frame (v8) — proposals tested against Elsner's three invariants; sdk_impact and discrepancy types remain. See PATCH_privacy_architecture_first.md.

Lenses

Lens Module / UI
Approval chains (tech ↔ economics ↔ collision) approval_chains.py · Intelligence
Know vs assume story.py + detection.py
Deep scan (proposals / issues / workflows) deep_scan.py
Focus filters sticky severity chips → cards; Action row narrows within Focus
Product lens (sdk / ledger / splice) da_product_context.py · grounding + Reference strip only — same cards

Product lens is the TPM view (ARCH_NOTE). It does not change classification; it reorders grounding emphasis and the Reference strip. Config: product_lens · CLI: scanner.py --lens.

Out of scope (confirmed cut)

Deferred polish

Fork radar + snapshots · pulse sparklines · fuller budget parse from proposal markdown.
(Corpus-backed Patterns / Predictions are live; grant-execution lists stay Admin corpus — not a chip.)

← All groundingDashboard↑ Back to top