Skip to content

docs(agents): point at the epic progress posts rule and the two skills (Closes #12629) - #12634

Merged
gHashTag merged 2 commits into
masterfrom
lane/epic-posts-rule-12629
Oct 26, 2026
Merged

gHashTag merged 2 commits into
masterfrom
lane/epic-posts-rule-12629

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

Closes #12629. See #12387 (the first initiative whose progress is posted this way) and #12630 (where tri blog becomes a real spec-first subcommand).

What

One new section at the end of AGENTS.md, ## Epic progress posts, eleven lines, a pointer and not the rule (the "Don't hand-copy a rule" law: the long form lives in one place and every other file points at it).

The same section, with full Trinity-S-AI-DNA/t27#N references, goes to gHashTag/trinity, gHashTag/trinity-fpga and gHashTag/igla-coder-gpu in one PR each (FR-002 of #12629).

Checks

🤖 Generated with Claude Code

Closes #12629)

One new section at the end of AGENTS.md, a pointer and not the rule: every epic and
every initiative (issue -> epic -> initiative, label `initiative`, the three most
prioritized pinned) carries public progress posts in one house format, a .t27 card
with the percent, the breakthroughs and the blockers, redrawn after every iteration.
The rule lives in the skill `epic-progress-posts`, the publication path in the skill
`tri-blog`; a `blog` subcommand of the built `tri` does not exist yet (#12630); the
first dashboard run this way is #12387.

Owner, 2026-10-26 (translated): write this into the AGENTS.md rules of the key
projects and create skills for fast publication.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-26 04:51:32 UTC

Summary

Status Count
Total Open PRs 22
PRs with Failing Checks 20
PRs with All Checks Green 2
READY 0
FAILING 20
PENDING 0
NO CHECKS YET 1

These columns do not partition: 0 + 20 + 0 + 1 = 21, and there are 22 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=6fb540d220f7 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@tri-claw

tri-claw Bot commented Oct 26, 2026 •

Copy link
Copy Markdown

Summary by t27-bees

This change adds a documentation section to AGENTS.md that points agents toward two skills (epic-progress-posts and tri-blog) for creating and publishing epic/initiative progress posts, without duplicating the rules themselves.

Worth a look


Read: 1 files, +12 -0, the whole diff. Head 021291c. Model: openai-compatible/nvidia/nemotron-3-ultra-550b-a55b. Commands: @t27-bees review | summary | help | pause | resume. Free for every repository.

@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-26 05:12:12 UTC

Summary

Status Count
Total Open PRs 21
PRs with Failing Checks 19
PRs with All Checks Green 2
READY 0
FAILING 19
PENDING 0
NO CHECKS YET 1

These columns do not partition: 0 + 19 + 0 + 1 = 20, and there are 21 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=6fb540d220f7 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag

Copy link
Copy Markdown
Collaborator Author

The coverage red on this head is master's own, not this PR's. The job Every seal still describes its spec fails on master itself (Seal Coverage runs 40271326185 on 833925fe47 and 40273324519 on 2283ad50c8) with eleven seals that newly do not hold: ten [stale] (cli_git_commands, crons_t27os-night-loop, git_commands, t27b_T27bWasm, t27f_T27fWorkGraph, t27f_a11y_mirror, t27f_hud, t27os_T27osHiveFeedAcceptance, t27os_T27osLabLegs, t27os_labs) and queen_local_dispatch as [gen-drift]. This PR touches none of those specs or seals. The refresh is #12626 (seals/corpus-refresh); no second fix is filed here. Nothing is pushed for this red: a reviewer can discount coverage while master's own run of the job fails, and this branch takes a clean merge of master once the refresh lands.

🤖 Addressed by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Epic progress posts: the rule in AGENTS.md of the key projects and the skills epic-progress-posts and tri-blog

1 participant