-
Notifications
You must be signed in to change notification settings - Fork 16
chore: baseline converge (CI fix + agent stack) #36
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.
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
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,98 @@ | ||
| # AGENTS.md | ||
|
|
||
| Project agent rules. | ||
|
|
||
| <!-- DOX:BEGIN (canonical: github.com/agent0ai/dox AGENTS.md — always-latest copy; safe to edit/extend the block below, e.g. fill in Child DOX Index) --> | ||
| # DOX framework | ||
|
|
||
| - DOX is highly performant AGENTS.md hierarchy installed here | ||
| - Agent must follow DOX instructions across any edits | ||
|
|
||
| ## Core Contract | ||
|
|
||
| - AGENTS.md files are binding work contracts for their subtrees | ||
| - Work products, source materials, instructions, records, assets, and durable docs must stay understandable from the nearest applicable AGENTS.md plus every parent AGENTS.md above it | ||
|
|
||
| ## Read Before Editing | ||
|
|
||
| 1. Read the root AGENTS.md | ||
| 2. Identify every file or folder you expect to touch | ||
| 3. Walk from the repository root to each target path | ||
| 4. Read every AGENTS.md found along each route | ||
| 5. If a parent AGENTS.md lists a child AGENTS.md whose scope contains the path, read that child and continue from there | ||
| 6. Use the nearest AGENTS.md as the local contract and parent docs for repo-wide rules | ||
| 7. If docs conflict, the closer doc controls local work details, but no child doc may weaken DOX | ||
|
|
||
| Do not rely on memory. Re-read the applicable DOX chain in the current session before editing. | ||
|
|
||
| ## Update After Editing | ||
|
|
||
| Every meaningful change requires a DOX pass before the task is done. | ||
|
|
||
| Update the closest owning AGENTS.md when a change affects: | ||
|
|
||
| - purpose, scope, ownership, or responsibilities | ||
| - durable structure, contracts, workflows, or operating rules | ||
| - required inputs, outputs, permissions, constraints, side effects, or artifacts | ||
| - user preferences about behavior, communication, process, organization, or quality | ||
| - AGENTS.md creation, deletion, move, rename, or index contents | ||
|
|
||
| Update parent docs when parent-level structure, ownership, workflow, or child index changes. Update child docs when parent changes alter local rules. Remove stale or contradictory text immediately. Small edits that do not change behavior or contracts may leave docs unchanged, but the DOX pass still must happen. | ||
|
|
||
| ## Hierarchy | ||
|
|
||
| - Root AGENTS.md is the DOX rail: project-wide instructions, global preferences, durable workflow rules, and the top-level Child DOX Index | ||
| - Child AGENTS.md files own domain-specific instructions and their own Child DOX Index | ||
| - Each parent explains what its direct children cover and what stays owned by the parent | ||
| - The closer a doc is to the work, the more specific and practical it must be | ||
|
|
||
| ## Child Doc Shape | ||
|
|
||
| - Create a child AGENTS.md when a folder becomes a durable boundary with its own purpose, rules, responsibilities, workflow, materials, or quality standards | ||
| - Work Guidance must reflect the current standards of the project or user instructions; if there are no specific standards or instructions yet, leave it empty | ||
| - Verification must reflect an existing check; if no verification framework exists yet, leave it empty and update it when one exists | ||
|
|
||
| Default section order: | ||
| - Purpose | ||
| - Ownership | ||
| - Local Contracts | ||
| - Work Guidance | ||
| - Verification | ||
| - Child DOX Index | ||
|
|
||
| ## Style | ||
|
|
||
| - Keep docs concise, current, and operational | ||
| - Document stable contracts, not diary entries | ||
| - Put broad rules in parent docs and concrete details in child docs | ||
| - Prefer direct bullets with explicit names | ||
| - Do not duplicate rules across many files unless each scope needs a local version | ||
| - Delete stale notes instead of explaining history | ||
| - Trim obvious statements, repeated rules, misplaced detail, and warnings for risks that no longer exist | ||
|
|
||
| ## Closeout | ||
|
|
||
| 1. Re-check changed paths against the DOX chain | ||
| 2. Update nearest owning docs and any affected parents or children | ||
| 3. Refresh every affected Child DOX Index | ||
| 4. Remove stale or contradictory text | ||
| 5. Run existing verification when relevant | ||
| 6. Report any docs intentionally left unchanged and why | ||
|
|
||
| ## User Preferences | ||
|
|
||
| When the user requests a durable behavior change, record it here or in the relevant child AGENTS.md | ||
|
|
||
| ## Child DOX Index | ||
|
|
||
| This project is not yet indexed. Before continuing you must scan the project, build the DOX tree and replace this message with the actual index. Go deep and scan files recursively to properly evaluate complexity and create nested DOX files where needed. | ||
|
antongulin marked this conversation as resolved.
|
||
| <!-- DOX:END --> | ||
|
|
||
| <!-- BASELINE:BEGIN (managed by agents-md-bootstrap) --> | ||
| ## Engineering baseline | ||
|
|
||
| This repo follows the baseline: `~/Code/700 systems/baseline` (https://github.com/antongulin/baseline, private). | ||
| Read `baseline/00-laws.md` first; pillars 01–07 hold the law (workspace, agents, project, | ||
| stacks, infra, delivery, knowledge). Answer standards questions from those files, not memory. | ||
| Anything missing or broken against the baseline is surfaced loudly — never skipped (law 2). | ||
| <!-- BASELINE:END --> | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| AGENTS.md |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| AGENTS.md |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.