Skip to content

Merge main's agent context into the rule-records stack - #531

Closed
sam-aydlette wants to merge 8 commits into
feat/frr-recordsfrom
chore/sync-main-into-stack
Closed

sam-aydlette wants to merge 8 commits into
feat/frr-recordsfrom
chore/sync-main-into-stack

Conversation

@sam-aydlette

Copy link
Copy Markdown
Owner

SCN-Type: not-significant
SCN-Rationale: Brings main's agent context into the stack; no change to how security posture is verified or published.

Changed

  • Merges main (agent context from Agent context: slim CLAUDE.md, two skills, guardrails, latitude rule #530) into feat/frr-records.
  • CLAUDE.md conflict resolved with main's structure and wording. That includes the Proof-of-concept latitude section in its amended form, which makes docs(CLAUDE.md): looser Simulated criterion #522's change redundant.
  • Added for this stack only:
    • the three unattended evidence workflows in the deploy invariant;
    • a rule-records invariant (data/frr-records.json, scripts/_frr.py);
    • frr-records.json in the registers row;
    • the nightly's publish list described by its publish step, not a fixed count.

Effect

None on published output beyond what #530 already changes (sitemap.xml). Branches stacked on feat/frr-records pick up the new agent context when they merge it.

Verified

make check exit 0 on the merged tree. This includes #530's new tests (sitemap, homepage cards, agent-context paths), which now run against the stack.

Residual / needs human

Couldn't verify

Nothing outstanding.

Follow-ups noticed

None.

🤖 Generated with Claude Code

sam-aydlette and others added 8 commits November 6, 2026 19:53
…ne skills

CLAUDE.md keeps the always-true rules: invariants, the repo map, PR rules,
and a plan gate with a scope tripwire in place of open-ended autonomy.
Procedures move into two project skills that load only when a task needs
them. Out-of-date references (ground-truth.md, the SSP, POA&M entries,
make targets that live in infrastructure/Makefile) are corrected.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EPMbZUHNXLjJxbN2HEPpVs
Articles 22, 24, 25 and 26, the contact page, and three research pages
(authorization-boundary, staying-in-the-loop, vulnerability-evidence) were
served but absent from sitemap.xml. lastmod is each article's index date;
for the contact and authorization-boundary pages it is the last commit date.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EPMbZUHNXLjJxbN2HEPpVs
.claude/settings.json denies force-pushes, terraform destroy and aws s3 rm,
and asks the operator before terraform apply, apply-infra/pipeline, pushes
to main, gh pr merge, IAM writes and S3 writes. Pushes to branches stay
unprompted, so small tasks still go straight to a PR.

.claude/hooks/stop-check.sh runs make check at the end of a turn when the
working tree has changes, and blocks the stop while it fails. Missing tools
produce a visible non-blocking notice instead of a block.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EPMbZUHNXLjJxbN2HEPpVs
Three hand-maintained copies had no check: sitemap.xml (eight live pages
missing), the homepage's Recent Articles cards, and the paths named in
CLAUDE.md and the skills (the old CLAUDE.md named a file that did not
exist). Each test was confirmed to fail on the drift it targets. CLAUDE.md
and the site-content skill now say what is enforced.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EPMbZUHNXLjJxbN2HEPpVs
Adds CLAUDE.md §6: lead with the outcome, keep verified separate from
assumed, push back before acting on a plan that looks wrong, and no
opening praise. Unprompted ideas are capped at three, each with why it
matters, and "none" is a valid answer; they are never built unasked.
When the operator asks for ideas, range widely.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EPMbZUHNXLjJxbN2HEPpVs
…d Effect in PR bodies

The slim CLAUDE.md keeps the operator's Proof-of-concept latitude section
word for word (the four statuses, the stand-in test, who approves stand-ins
and scope cuts, never choosing a status because a gate requires it), in the
form amended on the rule-records stack. The PR-body rule now starts with the
SCN lines the SCN gate reads and includes an Effect section. References to
scripts/staged/ go, since that directory is being removed, and the nightly's
write scope is described by its role policy rather than a fixed prefix.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Agent context: slim CLAUDE.md, two skills, guardrails, latitude rule
CLAUDE.md takes main's structure and wording. Added for this stack: the
three unattended evidence workflows, the rule-records invariant, and the
registers row; the nightly's publish list is described by its step.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sam-aydlette
sam-aydlette marked this pull request as draft November 7, 2026 20:56
@sam-aydlette

Copy link
Copy Markdown
Owner Author

Closed without merging. The work is kept locally and will land on main in smaller slices, each deployed and verified.

@sam-aydlette
sam-aydlette deleted the chore/sync-main-into-stack branch November 7, 2026 21:43
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.

1 participant