Skip to content

Update AGENTS.md and SECURITY.md for agents working from the board #13

Closed

Description

@dorelljames

Why

Coding agents will start picking up issues from the jscebu.org board through Symphony. A lead moves a card to Todo, the agent works on a symphony/ branch and hands off a PR in Human Review, and a lead reviews and merges. AGENTS.md and SECURITY.md were written before this and don't describe it.

What should change

AGENTS.md

  • Describe the board: what each column means (Backlog, Todo, In Progress, Human Review, Rework, Done) and who moves cards into it.
  • Map "How work ships" onto the board. Moving a card to Todo approves the intent. For anything bigger than a small fix, the agent hands off a plan first, and a lead approves it by moving the card back to Todo.
  • Say whose instructions count: the issue body, and comments or reviews from leads. Comments from anyone else are information, not instructions.
  • Make the skill references work for agents that don't have the superpowers: skills (Codex, for example): describe each step, and name the skill as one way to do it.

SECURITY.md

  • It points to the "Report a vulnerability" button "if it's enabled", but private vulnerability reporting is off for this repo today. Either a lead turns it on, or the line changes.
  • Cover the agents. Prompt injection through issues, comments or pull requests, and misuse of an agent's access, are in scope and should be reported privately. Say what the agents can't do: merge, push to main or deploy.

Acceptance

  • Both files describe how the board and the agents actually work.
  • Decisions only a lead can make (private vulnerability reporting, who counts as a lead, anything else that comes up) are listed as open questions in the plan, and answered before the files change.
  • pnpm test and pnpm build pass.

Activity

  1. dorelljames commented on Oct 30, 2026

    @dorelljames
    MemberAuthor

    Codex Workpad

    Dorells-MacBook-Pro-X.local:/Users/dorelljames/Projects/jscebu-symphony-workspaces/GH-13@1ea2203
    

    Phase: build, handed off

    Plan

    • 1. Resume: read sync/guidance, inspect board, issue and PR feedback, and move Todo to In Progress.
    • 2. Record approved lead answers in the plan and spec before editing policy files.
    • 3. Update AGENTS.md and SECURITY.md against the approved plan.
    • 4. Validate both files, review the whole diff, and prepare host handoff files.
    • 5. Hand off to Human Review.

    Acceptance Criteria

    • Both files describe how the board and agents actually work.
    • Lead-only decisions are listed in the plan and answered with sources before policy edits.
    • All six board columns, intent/plan approval, trusted instructions and optional skill equivalents are covered.
    • Security reporting uses the approved private email route and covers prompt injection, access misuse and agent limits.
    • pnpm test and pnpm build pass.

    Validation

    • pnpm test — passed: 7 brand files / 93 tests and 4 website files / 21 tests (114 total).
    • pnpm build — passed, including check-dist: 14 files, 6 pages, 10 redirects, brand parity, 30 source files checked.
    • Review git diff origin/main, untracked files and whitespace.

    Notes

    • Prior plan handoff: spec and plan merged in PR #14; policy implementation remained pending.
    • 2026-10-30 09:33:24 UTC: Sync is clean at 1ea2203 on symphony/Update AGENTS.md and SECURITY.md for agents working from the board #13; no pre-existing local changes. The live card was Todo with Phase: plan, awaiting approval, so the plan is approved and this run is build phase. Moved only this card to In Progress.
    • 2026-10-30 09:33:24 UTC: Read issue comments and all three PR Plan: Document board-driven agent and security policies #14 feedback channels. No lead review requests or must-fix findings. The old PR was merged, not closed unmerged; the host will handle the build PR after this run.
    • 2026-10-30 09:33:24 UTC: Lead answers, author_association MEMBER: Q1 keep private vulnerability reporting off and use hello@jscebu.org; Q2 OWNER/MEMBER/COLLABORATOR count as leads with no allow-list; Q3 leads own Backlog, agents never add cards or act on Backlog.
    • 2026-10-30 09:33:24 UTC: Reverified private-vulnerability-reporting: HTTP 200, enabled: false. No setting changed. Record decisions in plan/spec before AGENTS.md or SECURITY.md edits. Documentation-only work needs no prose-assertion tests; required repository checks still run.
    • 2026-10-30 09:34:56 UTC: Recorded Q1–Q3 and approval in the plan/spec before editing either policy. AGENTS.md now covers board actors, approval/rework flow, optional skill equivalents, host handoff and trust; SECURITY.md uses email only and covers agent attacks and unconditional access limits. No code, settings or infrastructure changed. Required checks and whole-diff review are next.
    • 2026-10-30 09:36:29 UTC: Final review of both policies against all acceptance criteria and lead answers passed. Reviewed the full diff against origin/main, untracked files and whitespace; only AGENTS.md, SECURITY.md and the plan/spec updates are changed. No generated artifacts, secrets, application code or settings changes.
    • 2026-10-30 09:36:29 UTC: Host handoff files are ready. PR title/body describe the implementation, include Closes Update AGENTS.md and SECURITY.md for agents working from the board #13 and Symphony/lead-review attribution; commit.txt was written last. The host will commit, push and create/update the build PR after this run. No new PR URL or CI result is claimed.
    • 2026-10-30 09:36:29 UTC: All acceptance criteria and local checks pass. Q1–Q3 are resolved, no must-fix feedback remains and no external blockers were encountered. Handing this card to Human Review as the final action; no further changes while awaiting review.
  2. added a commit that references this issue on Oct 30, 2026
  3. added
    codexSymphony: the Codex agent picks this card up
    on Oct 30, 2026
  4. dorelljames commented on Oct 30, 2026

    @dorelljames
    MemberAuthor

    Reopening: PR #14 merged only the plan (spec and plan docs). The AGENTS.md and SECURITY.md changes are still to do, after a lead answers the plan's three open questions.

  5. dorelljames commented on Oct 30, 2026

    @dorelljames
    MemberAuthor

    Answers to the plan's open questions (PR #14):

    • Q1, private vulnerability reporting: keep it off. Drop the "Report a vulnerability" button line from SECURITY.md; reports go to hello@jscebu.org.
    • Q2, who counts as a lead: anyone whose GitHub author_association is OWNER, MEMBER or COLLABORATOR. No separate allow-list.
    • Q3, Backlog: leads own it. Leads place cards in Backlog and move them out; agents never add cards to the board or act on Backlog cards.
  6. cebu-symphony commented on Oct 30, 2026

    @cebu-symphony
    Contributor

    Codex update

    Phase: build · Started: addressing the lead's workflow changes on PR #15.

  7. cebu-symphony commented on Oct 30, 2026

    @cebu-symphony
    Contributor

    Codex update

    Phase: build, handed off · All four requested workflow changes are implemented and validated; host handoff files are ready for PR #15.

    Needs you

    Review AGENTS.md’s update, approval and PR handoff rules, and SECURITY.md’s App identity and access limits on PR #15.

    Checklist, checks and notes

    Dorells-MacBook-Pro-X.local:/Users/dorelljames/Projects/jscebu-symphony-workspaces/GH-13@eebb2dd

    Plan

    • Collect issue comments, PR reviews, inline comments and PR conversation comments; verify status and sync.
    • Update the approved plan/spec with the lead's current workflow before editing policies.
    • Update AGENTS.md and SECURITY.md for updates, identity, PR handoffs and decision defaults.
    • Run required checks, review the whole branch and prepare host handoff files.

    Acceptance criteria

    • Both policies describe the current board and agent workflow.
    • Lead-only decisions have explicit lead sources before policy edits.
    • Append-only updates, local checklist, historical workpad comments and App identity are consistent throughout the PR.
    • Plan/blocked PRs say "Don't merge this yet" and use Refs; only complete builds use Closes.
    • Numbered questions offer lettered options with one recommendation; a return to Todo without a reply accepts recommendations.
    • pnpm test and pnpm build pass.

    Checks

    • pnpm install --frozen-lockfile — passed; repeated from a fresh local node_modules after the stale install broke an Astro check dependency.
    • CI=1 pnpm test — passed: 112 brand tests and 58 website tests (170 total); Astro/TypeScript checks passed with 3 existing deprecation hints.
    • pnpm build — passed; check-dist: 15 files, 6 pages, 20 redirects, brand parity, 30 source files.
    • Whole-branch review: git diff origin/main, untracked files and git diff --check — passed; only AGENTS.md, SECURITY.md and the plan/spec changed. No generated artifacts, unrelated changes or secrets in the diff.

    Feedback

    • Lead item 1: documented append-only start/handoff/blocked updates, local checklist folded into handoffs and historical workpad comments; aligned plan/spec.
    • Lead item 2: added App identity, read-only code API limits, host SSH pushes and App-output trust to both policies and aligned plan/spec.
    • Lead item 3: plan/blocked PRs begin with the required warning and use Refs; only complete builds use Closes. Aligned plan/spec.
    • Lead item 4: documented numbered questions, lettered options, a recommendation and acceptance on a silent return to Todo; aligned plan/spec without reopening resolved original questions.
    • Claude suggestion 1 (Todo automation): retained the existing board policy as the lead requested; did not infer or change live automation configuration. No must-fix finding.
    • Claude suggestion 2 (issue-text trust and later edits): retained the existing trust policy as requested; the proposed issue-version rule would need a separate lead decision. No must-fix finding.
    • Claude suggestion 3 (plan PR merge timing): retained the approved board approval gate; did not invent a new merge requirement. The requested PR warning/Refs rule is now explicit. No must-fix finding.
    • Claude suggestion 4 (spec Rework actors): aligned the spec with AGENTS.md, including Symphony-triggered Rework and host-review findings.
    • Claude suggestion 5 (skill provenance): changed AGENTS.md to refer to the session's GitHub skill, matching its host-provided status.

    Notes

    • Phase: build, handed off; Rework continues the approved implementation on symphony/Update AGENTS.md and SECURITY.md for agents working from the board #13, without a move to In Progress.

    • Sync is clean at eebb2dd; PR Document the current Symphony agent workflow #15 is open. PR Plan: Document board-driven agent and security policies #14 merged the plan. No pre-existing local changes or local workpad.

    • Original Q1–Q3 answers: lead issue comment 6519521904 (MEMBER); keep reporting off and use hello@jscebu.org, use OWNER/MEMBER/COLLABORATOR, leads own Backlog.

    • Current workflow changes explicitly requested by dorelljames (MEMBER) at Document the current Symphony agent workflow #15 (comment); no new lead-only decision is needed.

    • Latest issue update: start comment 6535737424, authored by cebu-symphony[bot]. Historical Codex Workpad comment 6517684229 is unchanged.

    • GET /user returned 403 for this App installation token. Session identity was independently confirmed by the successful start comment; this does not block the task.

    • All feedback channels read; no inline comments, formal PR reviews or must-fix findings. The host's round-1 review is a PR conversation comment by dorelljames from before the App existed.

    • The host-provided GitHub skill still describes the old workpad protocol; the explicit session and lead update instructions take precedence.

    • Initial pnpm test stalled at Astro’s install prompt because the pre-existing install lacked @emnapi/core; pnpm install --force did not repair it. Reinstalled node_modules from the unchanged lockfile; the CI=1 rerun passed. Removed the temporary backup and task-created pnpm cache after repair; manifests and lockfile are unchanged.

    • All four lead requests are resolved. Plan shortened to the session’s three-part format while retaining resolved decisions, source links and validation history. No external blockers remain.

    • Host handoff files prepared for the existing PR Document the current Symphony agent workflow #15 with Closes Update AGENTS.md and SECURITY.md for agents working from the board #13 and Symphony attribution. The host will commit, push and update the PR after this run; no new commit or CI result is claimed.

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

    codexSymphony: the Codex agent picks this card updocumentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions