Skip to content

docs(agents): describe the tree as it is now - #7

Merged
Aswin-V merged 1 commit into
embeddedos-org:masterfrom
Greeva48:docs/agents-md-current-tree
Nov 9, 2026
Merged

Aswin-V merged 1 commit into
embeddedos-org:masterfrom
Greeva48:docs/agents-md-current-tree

Conversation

@Greeva48

@Greeva48 Greeva48 commented Nov 9, 2026 •

Copy link
Copy Markdown
Contributor

What changed

AGENTS.md still described the first version of the repository: only README.md, LICENSE and .gitignore, no workflows, no SECURITY.md. This PR updates three passages; only AGENTS.md changes.

  • Intro: still "Placeholder repository (Status: Planned)" with no implementation, manifests or tests. It now says what the repository holds (SECURITY.md, .well-known/security.txt, docs under docs/) and exactly what the docs workflow checks: the docs, the README and security.txt, but not SECURITY.md or AGENTS.md.
  • Build / test / lint: names the one verified command, python3 ci/check_docs.py, which is what .github/workflows/ci.yml runs, and says what it checks (taken from the script's docstring).
  • Security: points to SECURITY.md, docs/cvd-intake.md and .well-known/security.txt instead of saying no policy exists. It keeps "do not report in public issues". It does not name a reporting channel; SECURITY.md is the single source for that.

This PR removes the Security section's Background: [docs/wiki/Security.md](docs/wiki/Security.md) link. That page still says "No root SECURITY file was found", which is now wrong, so linking to it as background would repeat the stale claim. The file itself is not changed: it is a mirror of the wiki and records the commit it inspected.

The "Status: Planned" wording is kept as it was; whether it should change is a maintainer decision.

Fixes #6

Previews

AGENTS.md check and diff

Validation

Check Command Result
AGENTS.md vs tree, before (fda68eb) agents-check.sh fda68eb1 FAIL (expected): 4 stale statements (no SECURITY.md, no workflows, "only 3 files", no command named)
AGENTS.md vs tree, after agents-check.sh <head> PASS
Repo docs check python3 ci/check_docs.py PASS: "OK: 12 docs checked, one H1 each, all relative links resolve"
Whitespace git diff --check fda68eb1 HEAD PASS

agents-check.sh lists the tree at a ref and fails when AGENTS.md at that ref states something the tree contradicts.

Summary by Sourcery

Bring AGENTS.md up to date with the repository’s current documentation, automation, and security guidance.

Enhancements:

  • Update AGENTS.md to accurately describe the repository contents, documentation validation command, and current security resources.

Documentation:

  • Document the repository’s current security policy, vulnerability intake guidance, security.txt contact file, and documentation checks.

AGENTS.md said the tree held only README.md, LICENSE and .gitignore,
with no workflows and no SECURITY.md. The repository now has the org
CVD policy, security.txt, the CRA and Mbed TLS docs and a docs-check
workflow. Name the one verified command (ci/check_docs.py) and point
the Security section at SECURITY.md.
@coderabbitai

coderabbitai Bot commented Nov 9, 2026

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: ae0e2a21-b4ca-44ab-b123-03b28c76b990
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@qodo-code-review

Copy link
Copy Markdown

ⓘ Your Qodo trial ends soon. Ask your workspace admin to set up billing to keep reviews running after the trial. Manage billing

@kody-ai

kody-ai Bot commented Nov 9, 2026

Copy link
Copy Markdown

You've used all your free Kodus-paid PR reviews 🎁

Your trial is still active — this just means the PR reviews we cover during the trial are used up.

Connect your own AI key to keep Kody reviewing — unlimited reviews, on any plan (Free included).

Want more trial reviews to finish evaluating before adding a key? Talk to our founders. 😎

@sourcery-ai

sourcery-ai Bot commented Nov 9, 2026 •

Copy link
Copy Markdown

Reviewer's Guide

Documentation

Update AGENTS.md to describe the repository’s current security and documentation files, the docs-check command, and the current vulnerability-disclosure policy.

  • AGENTS.md L3-8, L13-24, L33-37

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Align AGENTS.md with the current repository and security policy

📝 Documentation 🕐 Less than 10 minutes

Grey Divider

AI Description

• Replace stale repository and automation claims with the current documentation and CI scope.
• Document the verified docs-check command and its validation coverage.
• Point security guidance to the current policy, intake template, and contact file.
Diagram

graph TD
  A["Agent notes"] -->|documents| B["Docs workflow"] -->|runs| C["Docs checker"] -->|validates| D["Docs and README"]
  C -->|validates| E["Security contact"]
  A -->|points to| F["CVD policy"] -->|links to| G["Intake template"]
  A -->|points to| E
Loading
High-Level Assessment

Keep AGENTS.md as a concise guide to the existing workflow and security sources. Duplicating reporting channels or policy text here would create another place for that guidance to become stale.

Files changed (1) +23 / -10

Documentation (1) +23 / -10
AGENTS.mdCorrect repository, validation, and security guidance +23/-10

Correct repository, validation, and security guidance

• Replaces outdated claims about the repository and names the CI-verified docs-check command and its scope. Links to the current CVD policy, intake template, and security contact file instead of the stale wiki background link, while retaining the warning against public vulnerability reports.

AGENTS.md

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Qodo Logo

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 3 issues

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="AGENTS.md" line_range="22" />
<code_context>
+```
+
+It needs only the Python standard library. It checks that each doc under
+`docs/` and the README has one H1, that relative links resolve, and that
+`.well-known/security.txt` has `Contact` and `Expires` and has not expired.
+Do not invent other commands.
</code_context>
<issue_to_address>
**Sidebar H1 coverage is overstated**

When an agent relies on the stated H1 coverage for `docs/wiki/_Sidebar.md`, `check_h1` exempts `docs/wiki/_Sidebar.md`, so the check passes even when that file has no H1 and agents get a false validation guarantee.

Document that `docs/wiki/_Sidebar.md` is exempt from the H1 check.
</issue_to_address>

### Comment 2
<location path="AGENTS.md" line_range="4-6" />
<code_context>
-tests, or automation exist on `master` yet. The code that will become eSec
-lives in [`embeddedos-org/eos`](https://github.com/embeddedos-org/eos) at
+Placeholder repository (Status: Planned). No implementation, build manifests
+or tests exist on `master` yet. The repository holds the org security policy
+(`SECURITY.md`, `.well-known/security.txt`) and security docs under `docs/`.
+A docs workflow checks those docs, the README and `security.txt` (not
+`SECURITY.md` or this file). The code that will become eSec lives in
+[`embeddedos-org/eos`](https://github.com/embeddedos-org/eos) at
</code_context>
<issue_to_address>
**Docs describe an available CI command**

AGENTS.md now says the repository has a docs workflow and names a verified docs-check command, contradicting the entry's claims that there are no workflows or verified commands and that the tree holds only three files.

Update the knowledge entry to reflect the repository's current contents and docs-check workflow.

Also at `AGENTS.md:15-18`.
</issue_to_address>

### Comment 3
<location path="AGENTS.md" line_range="5" />
<code_context>
-lives in [`embeddedos-org/eos`](https://github.com/embeddedos-org/eos) at
+Placeholder repository (Status: Planned). No implementation, build manifests
+or tests exist on `master` yet. The repository holds the org security policy
+(`SECURITY.md`, `.well-known/security.txt`) and security docs under `docs/`.
+A docs workflow checks those docs, the README and `security.txt` (not
+`SECURITY.md` or this file). The code that will become eSec lives in
</code_context>
<issue_to_address>
**Security policy is now referenced**

AGENTS.md now identifies `SECURITY.md` as the organization's disclosure policy, contradicting the entry's claim that the file does not exist.

Update the knowledge entry to reflect the current presence of `SECURITY.md`.

Also at `AGENTS.md:33-34`.
</issue_to_address>

Linked issues

#6 AGENTS.md says the tree has only README/LICENSE/.gitignore, no workflows and no SECURITY.md · 3 of 3 met

# Requirement Status Notes
1 Describe the current tree instead of claiming it contains only README.md, LICENSE and .gitignore or has no workflows. ✅ Met The intro now names the policy, security.txt and docs, and describes the docs workflow and what it checks.
2 State that there is no code or tests and name the verified command, python3 ci/check_docs.py. ✅ Met The Build / test / lint section says there is no source code or tests and documents the command run by CI.
3 Identify SECURITY.md as the security policy. ✅ Met The Security section describes SECURITY.md as the organization’s coordinated vulnerability disclosure policy.

Sourcery assessment

Approval pending. 2 findings to address first.

Blocking findings: AGENTS.md:6, AGENTS.md:5


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread AGENTS.md
```

It needs only the Python standard library. It checks that each doc under
`docs/` and the README has one H1, that relative links resolve, and that

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚪ Low · Sidebar H1 coverage is overstated

When an agent relies on the stated H1 coverage for docs/wiki/_Sidebar.md, check_h1 exempts docs/wiki/_Sidebar.md, so the check passes even when that file has no H1 and agents get a false validation guarantee.

Document that docs/wiki/_Sidebar.md is exempt from the H1 check.

Prompt for AI agents
In `AGENTS.md` at line 22:

**Sidebar H1 coverage is overstated**

When an agent relies on the stated H1 coverage for `docs/wiki/_Sidebar.md`, `check_h1` exempts `docs/wiki/_Sidebar.md`, so the check passes even when that file has no H1 and agents get a false validation guarantee.

Document that `docs/wiki/_Sidebar.md` is exempt from the H1 check.

Comment thread AGENTS.md
Comment on lines +4 to +6
or tests exist on `master` yet. The repository holds the org security policy
(`SECURITY.md`, `.well-known/security.txt`) and security docs under `docs/`.
A docs workflow checks those docs, the README and `security.txt` (not

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Medium · Docs describe an available CI command

AGENTS.md now says the repository has a docs workflow and names a verified docs-check command, contradicting the entry's claims that there are no workflows or verified commands and that the tree holds only three files.

Update the knowledge entry to reflect the repository's current contents and docs-check workflow.

Also at AGENTS.md:15-18.

Prompt for AI agents
In `AGENTS.md` at lines 4-6:

**Docs describe an available CI command**

AGENTS.md now says the repository has a docs workflow and names a verified docs-check command, contradicting the entry's claims that there are no workflows or verified commands and that the tree holds only three files.

Update the knowledge entry to reflect the repository's current contents and docs-check workflow.

Also at `AGENTS.md:15-18`.

From AGENTS.md L8-13:

## Build / test / lint

No verified commands exist: the tree holds only `README.md`, `LICENSE`, and
`.gitignore` — no manifest (`package.json`, `pyproject.toml`,
`CMakeLists.txt`), no workflows, no tests, and the README documents no
commands. Do not invent commands; re-check the README before running anything.

Comment thread AGENTS.md
lives in [`embeddedos-org/eos`](https://github.com/embeddedos-org/eos) at
Placeholder repository (Status: Planned). No implementation, build manifests
or tests exist on `master` yet. The repository holds the org security policy
(`SECURITY.md`, `.well-known/security.txt`) and security docs under `docs/`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Medium · Security policy is now referenced

AGENTS.md now identifies SECURITY.md as the organization's disclosure policy, contradicting the entry's claim that the file does not exist.

Update the knowledge entry to reflect the current presence of SECURITY.md.

Also at AGENTS.md:33-34.

Prompt for AI agents
In `AGENTS.md` at line 5:

**Security policy is now referenced**

AGENTS.md now identifies `SECURITY.md` as the organization's disclosure policy, contradicting the entry's claim that the file does not exist.

Update the knowledge entry to reflect the current presence of `SECURITY.md`.

Also at `AGENTS.md:33-34`.

From AGENTS.md L17, AGENTS.md L22:

No `CONTRIBUTING.md` exists. Keep changes scoped and follow the repository's

@Aswin-V
Aswin-V merged commit 045f298 into embeddedos-org:master Nov 9, 2026
6 checks passed
@Aswin-V

Aswin-V commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Premise: pass — master AGENTS.md stale: SECURITY.md, .well-known/security.txt, docs/, ci/ exist; ci/check_docs.py checks one-H1 + links as cited; fixes #6.
Contract: n/a — docs-only.
CI: https://github.com/embeddedos-org/eSec/pull/7/checks @ 7b400a6 (6 checks green).
Integration: n/a.
Reviewer: loop run 2026-11-09

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.

AGENTS.md says the tree has only README/LICENSE/.gitignore, no workflows and no SECURITY.md

2 participants