Skip to content

docs: where-to-file block in AGENTS.md; intake routes outsider reports to Discussions #425

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Jammy2211 merged 1 commit into from
Sep 27, 2026
Merged

docs: where-to-file block in AGENTS.md; intake routes outsider reports to Discussions #425

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -147,6 +147,20 @@ armed hourly check-ins on 2026-08-31, and a mobile `/prm` re-armed a 60-minute
`send_later` hourly all night on 2026-09-03 with no task active, draining usage.
<!-- repos_sync:deliverable:end -->

<!-- repos_sync:filing:begin -->
## Where to file

Questions, help with code or an analysis, ideas, bug reports and results from a
user or collaborator — or an agent acting for one — go to
<https://github.com/orgs/PyAutoLabs/discussions> in the matching category
(Help & Questions, Ideas & Proposals, Bugs & Errors, Show and tell;
Announcements is maintainers-only), never to this repo's Issues. An agent never
runs `gh issue create` for such a report: it drafts the title, category and
body and hands them to the human (sessions cannot create Discussions). Only the
development flow — Mind prompt → `/start_dev` → `/create_issue` → one issue per
task → PR — opens issues here. Why: `PyAutoMind/policy/community_surface.md`.
<!-- repos_sync:filing:end -->

Codex loads this repo's generated safety registrations from `.codex/hooks.json`
only after the project layer and exact current hook hash are reviewed and trusted
with `/hooks`; changed or untrusted hooks are skipped. The adapter registers the
Expand Down
5 changes: 5 additions & 0 deletions skills/intake/intake.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,6 +107,11 @@ dev workflow (issue, branch, plan). Do not bypass the Brain.
not infer, and a review is never a required step — the user asks for one, or
there isn't one. A declared review is also never demoted to `triage/`: with no
target resolved it files flat at `draft/human_review/<slug>.md`.
- **An outsider's report is not intake's to file.** A question, idea or bug
report from a user or collaborator (or their agent) belongs on the org
Discussions hub — draft the post (title, category, body) for the human per
`PyAutoMind/policy/where_to_file.md`; never a repo issue. Intake files a Mind
prompt only once the maintainer decides to act on such a report.
- Writes happen **only** under `--apply`; the default is a read-only dry run.
- **Machine sources** (scholar research runs, Heart findings, profiling
results) stage as provenance-tagged `ideas.md` bullets — `- [from: <source>]
Expand Down
Loading