Cyan Eclipse Awardline

Vendor: Cyan Eclipse Technologies · Platforms: MCP over stdio

What it does

• Novel mechanism (SPEC §2.1) — grant-term spending evidence: award terms are registered and sealed once; each item of spending is sealed against a specific term as it happens, hash-chained per award with a sealed running total; grant reports and drawdown audits are generated by recomputing from those receipts — the report is a view over evidence that already exists, not a reconstruction assembled at reporting time.
• Load-bearing label (verbatim, on every listing, manifest, and report-adjacent surface): an Awardline report is a recomputation from sealed receipts, not an audit, not an allowability determination, and not agency acceptance.
• Bench path: v0.1.0 bench (wave4/bench-awardline.md, defects D1–D5, conditions C1–C5) + v0.1.1 delta re-bench (wave4/rebench-awardline.md: D1–D5 all CLOSED, condition C4 SATISFIED, builder suite 26/26 reproduced, no new defect found).
• Standing conditions (from the re-bench): C1 — §10 counsel/govcon gate: unchanged, unbuilt, binds any real-award reliance. C2 — external anchor: unchanged; caps the verdict at PASS-CONDITIONAL. C3 — real Herald RS256: unchanged; required with re-bench before any live phase. C5 — name screen: "Awardline" remains a placeholder pending the trademark screen. (C4 — defect remediation + re-bench — is SATISFIED.)
• Awardline seals spend against term versions as registered by the grantee; a mis-registered term produces faithfully sealed evidence against the wrong terms, and detecting that is the grantee's review, not a recomputation result. Awardline is not an accounting system, not a grants-management system of record, not a bank or payment rail, not an auditor, and not a compliance determination. It does not move money, approve spending, decide allowability under an award, or file anything with any agency. Refusals are typed and seal nothing (e.g. SPEND_TERM_VERSION_MISMATCH, SPEND_CHAIN_MISMATCH). Herald (signing pattern), Meter (metering grammar), and Docket (pack grammar) are consumed by reference only.

Tools

Problems it addresses

• Grant reports get assembled at reporting time from spreadsheets and memory — a reconstruction, not evidence — and drawdown audits then re-litigate every line
• I need spending sealed against the award's terms as it happens, hash-chained per award with a sealed running total, so the report is generated by recomputing from receipts that already exist
• I need the honesty label load-bearing and verbatim: a recomputation from sealed receipts is not an audit, not an allowability determination, and not agency acceptance — and the tool must never move money, approve spending, or file anything

Not tested

• Any reliance on a real award — real award terms, real grantees, real funds, real drawdowns, agency reporting, or any government system is SPEC §10 counsel/govcon-gated (condition C1) and UNBUILT; v0.1.1 contains no dormant live path
• Audit, allowability, or agency acceptance — an Awardline report is a recomputation from sealed receipts, not an audit, not an allowability determination, and not agency acceptance; Awardline does not approve spending or decide allowability under an award
• Term-registration correctness — Awardline seals spend against term versions as registered by the grantee; a mis-registered term produces faithfully sealed evidence against the wrong terms, and detecting that is the grantee's review, not a recomputation result
• External anchoring / multi-party reliance — the pure local file store caps any verdict at PASS-CONDITIONAL (local/simulator) (condition C2); an external anchor is required before live or multi-party reliance
• Production signing — v0.1.1 signing is an HMAC fixture stand-in for Herald RS256 (condition C3: real Herald RS256 required with re-bench before any live phase; fixture keys in keys/, gitignored, mode 600)