Skip to content

Epic: GOLDEN CHAIN in t27 -- anchors, contribution ledger, usage from receipts, many signers, a live atlas #8609

Open

Description

@gHashTag

Brings the GOLDEN CHAIN design of gHashTag/golden-chain-international (Green Paper and White Paper v0.9, see gHashTag/golden-chain-international#140) into t27, the language and toolchain the network runs on. Every rule is written in .t27 and generated. Hand-written foreign code only shrinks (#8236).

What exists (2026-10-10)

What is missing

  • The anchor block (M0). t27's AGENTS.md has none yet, and the hub manifest format has not landed.
  • Contribution accounting. No record yet of who wrote which spec, and how much verified compute used it.
  • More than one signer. Without it, the t27b lab is a de facto chief validator, against S1.
  • An external anchor, so the manifest is not circular (RT-4).
  • A live atlas.
  • Legal gates before any value flow. These are red lines, not tasks for an agent.

Plan

Rules that do not bend

  • No chief validators: authority is a protocol rule plus a merged PR, never a person.
  • Accounting first, money last. No value moves until the white paper's gates are open: explorer-verified contracts, a fixed key registry, and written legal opinions.

Boundary

  • specs/queen/events.t27

Activity

  1. tri-claw commented on Oct 10, 2026

    @tri-claw

    The Queen cannot take this issue yet. A bee starts only on an issue whose body has every section below, and this one lacks:

    • missing: ## Boundary -- list every file this task may touch, one per line (- specs/x.t27); without it the Queen reserves nothing and no bee can take the issue
    • missing: ## User Scenarios -- at least one Given/When/Then scenario
    • missing: ## Requirements -- numbered obligations, FR-001: ... MUST ...
    • missing: ## Success Criteria -- an outcome a machine can settle: a number with a unit, a backticked file, exit 0, or a backticked command

    She tried to write them 2 times and could not (last: not a task: This is an epic tracking issue with a plan of sub-issues (#8603–#8607, gHashTag/trinity#1587), not an actionable task for a coding agent in this repository.). Add them and the next round takes it. The rule is specs/policy/issue_shape.t27.

  2. added
    needs-boundaryNo '## Boundary' section, so the Queen can reserve nothing for it and no bee can take it
    and removed
    needs-boundaryNo '## Boundary' section, so the Queen can reserve nothing for it and no bee can take it
    on Oct 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions