[sykosyber]

Admission

Class: R
Agent-platform: cursor
Reviewed-by: none recorded
Admitted-by: self (Class R)
Evidence: tested

Objective

Record, in the receipt CLI merged in #89, where Attest actually writes receipts, so nobody hardcodes .attest/receipts.

What changed

• examples/attest_receipt_observe.py: the module docstring and the receipt argument help now say that <attest_home> is Attest's --home, else $ATTEST_HOME, else .attest relative to Attest's working directory, and that .attest/receipts is only that default.

Source for the rule, read from SyberLabs/attest main (57874ba) and event-day (c4db73d): attest/pipeline.py sets ATTEST_DIR = Path(os.environ.get("ATTEST_HOME", ".attest")), attest/cli.py uses it as the --home default, and attest/loop.py:_write_receipt writes home / "receipts" / f"{case_id}.json".

The mismatch came from the original brief to Reason, which named .attest/receipts/<case>.json. #88's first commit (3a4354e) copied that path; 43f0302 corrected it to <attest_home>/receipts. Main and every open pull request now use <attest_home>/receipts.

What did not change

• No behavior change: the CLI still takes an explicit path, and receipts and observations stay verified: false.
• The schemas and golden traces are unchanged.

Evidence

PYTHONPATH=. python3 -m unittest discover -s tests -p test_attest_receipt_observe_example.py   # OK (7 tests)
python3 examples/attest_receipt_observe.py --help                                             # shows the new help text
python3 examples/attest_receipt_observe.py examples/fixtures/attest_receipt_v0_spec_sample.json   # prints the observation
git diff --check                                                                              # clean

Known limitations

• The rule describes Attest as of the commits above. If Attest changes how it resolves its home directory, this text has to follow.

  

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-25T22:32:15.829487Z	c5bec40	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.