Repository navigation
Give chat status answers dated sources and separate activation evidence #52
Description
The MIP-12 report exposed a gap in how chat communicates evidence. src/lib/ai/config.ts asks the model to cite a MIP number, while src/app/api/chat/route.ts injects a static bundle without a current-date or freshness contract. A proposal status can be repeated as a claim about whether a change is live on a network. The user has no linked activation evidence to inspect in that answer.
I want status answers to distinguish the proposal lifecycle from network activation and to show where the information came from.
Scope approved:
- Add consistent source/verification sections to the existing MIP knowledge documents: canonical specification URL and the date a maintainer checked it. Include separately sourced activation evidence where known. Missing evidence must remain explicit; a build or request timestamp is not a verification date.
- Add a server-owned instruction when assembling the chat request: status/activation answers should link the supplied official source and qualify dated evidence. A Final spec alone cannot prove mainnet activation. When activation evidence is absent or conflicting, say the bundle cannot confirm it and link the official reference.
- Include the current UTC date separately from the content verification date, and preserve the rule when an admin supplies a custom system prompt. Reuse the existing Markdown response rendering; do not add browsing, change the model or expand the agent's tools.
- Add offline tests capturing the real outgoing chat request with the provider mocked. Cover separately sourced Final/active information, Final with no activation evidence, and a custom prompt. Verify source URLs and dated instructions reach the provider; document a manual answer check without asserting model prose in a unit test.
The immediate stale MIP-12 facts are a separate correction. This issue owns the evidence format and request behavior, not upstream synchronization or a site-wide content rewrite.
Comment to claim and wait for maintainer approval before starting. One active claim per person across the pool.
Activity
ShadowOfTime1 commentedon Oct 4, 2026
I'd like to take this, admitted MOST participant.
Plan: add a "Sources and verification" section to each
content/mips/mip-*.mdwith the canonical spec URL, the date it was checked, and activation evidence with its own link, or an explicit "no activation evidence in this bundle" line. In the chat route I'll move prompt assembly into a small server-side helper that always appends the evidence rule and the current UTC date afterconfig.systemPrompt, so an Edge Config prompt can't drop it; no model, tool or rendering changes. Tests will call the realPOSThandler with botid, rate limit and the SiloRail client mocked, capture the outgoing messages, and cover Final with separate activation evidence, Final with no evidence, and a custom system prompt. I'll write the manual answer check up in the PR instead of asserting model prose.I'll wait for approval before writing code.
portdeveloper commentedon Oct 4, 2026
@ShadowOfTime1 approved, it's yours. Please coordinate the MIP-12 source section with #56 so its factual correction stays intact. The server-owned evidence rule should remain present with a custom admin prompt, as planned.