Skip to content

docs: Record security audit verdict - #23

Open
BenWestgate wants to merge 3 commits into
reviewability-v1from
20-security-audit-docs
Open

BenWestgate wants to merge 3 commits into
reviewability-v1from
20-security-audit-docs

Conversation

@BenWestgate

@BenWestgate BenWestgate commented Sep 22, 2026 •

Copy link
Copy Markdown
Owner

Record the finished 2026-09-22 python-codex32 security-audit verdict in a dedicated docs/audits/ directory.

Local planning, release-gate, helper-script, and unfinished review state remains ignored under docs/planning/; it is not part of this PR.

The verdict records confirmed findings, the falsified candidate, protocol/application hazards, and the required recovery boundary without changing normative security-model text ahead of the implementation fixes.

The current audit text also separates the two recovery threat models explicitly:

This removes the earlier implication that a 32-bit fingerprint must itself provide malicious-substitution resistance; closed #27 records that disposition. #43 tracks stronger human-record error detection and optional canonical single-sig descriptor-checksum evidence.

Refs #20.

Checks: documentation-only diff; links updated for the audit directory. The threat-model correction is commit f7b86cd.

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 00470b1f2b

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread .gitignore Outdated
Comment thread docs/planning/usability-appraisal.md Outdated
Comment thread docs/planning/build_alignment_report.py Outdated

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3bc520a5d3

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/security/audit-2026-09-22.md Outdated

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 30e54cab79

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/security/invariants.md Outdated
Comment thread docs/planning/resume_alignment_benchmarks.py Outdated
Comment thread docs/planning/resume_alignment_benchmarks.py Outdated

@baslabofhd777-lab baslabofhd777-lab 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.

yes

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c5ec185f0a

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/planning/build_alignment_report.py Outdated
Comment thread docs/planning/gui-plan.md Outdated
@BenWestgate

Copy link
Copy Markdown
Owner Author

Put planning back in .gitignore. this is a nightmare to review documents the world is not meant to see. Create a separate folder for audit results instead which are at least finished documents not subject to endless nit picking..

Keep local planning state ignored and publish only the finished audit result in a dedicated audit directory. This narrows the review surface to stable findings and their tracking references.

Refs #20.
@BenWestgate
BenWestgate force-pushed the 20-security-audit-docs branch from c5ec185 to dc0d70a Compare September 23, 2026 12:11
@BenWestgate BenWestgate changed the title docs: Restore audit planning and verdict docs: Record security audit verdict Sep 23, 2026

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dc0d70a46d

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/audits/security-2026-09-22.md
Comment thread docs/audits/security-2026-09-22.md Outdated
@BenWestgate BenWestgate added gate: adversarial review Resolve, merge, or explicitly defer before the next full adversarial review. area: security Security invariants, hardening, and security-sensitive boundaries. documentation Improvements or additions to documentation labels Sep 24, 2026

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f7b86cd9b7

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/audits/security-2026-09-22.md

@BenWestgate BenWestgate left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

AI-generated review (Claude), posted at the maintainer's request.

ACK f7b86cd, with one cross-PR conflict.

  • The accident-safety vs tampering split (#28/#57 vs #55) reads accurately, and the 32-bit grind point is stated without overclaiming.
  • #21 and #22 closed today. A one-line "Status: fixed in " under each would stop readers treating them as open. Same for #32 once #33 lands.
  • Nit: no trailing newline at EOF.

Comment thread docs/audits/security-2026-09-22.md

Copy link
Copy Markdown
Owner Author

Follow-up on the ACK nits: I’m not baking transient PR state into this historical verdict yet. The report intentionally records what was true at audited parent c118a83; #21/#22 are already fixed on reviewability-v1, #32 remains pending #33, and the restore finding remains pending #57/#28 integration. When those release-gate fixes land, add a compact “Status after audit” section (rather than rewriting each finding as if it were true at c118a83) and fix the EOF newline in that same doc-only touch. No security conclusion is blocked on those editorial nits.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: security Security invariants, hardening, and security-sensitive boundaries. documentation Improvements or additions to documentation gate: adversarial review Resolve, merge, or explicitly defer before the next full adversarial review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants