[ahrazzle]

protean-ops v1.0.0

The first release of the protean-ops ingredient, projected into a standalone
repository.

What this adds

• The five record-schema templates with their column contracts and an empty state.
• The five read-only gates that check them, parameterised by $PROTEAN_RECORDS_ROOT and
  defaulting to ./records, plus synthetic example records they run against.
• The role roster allowlist the rotation gate reads.

Plus the machine descriptor, the standalone installer, the declared gates, the
test suite, the MIT LICENSE, and the CI workflow.

Evidence register

Item	Command	Result
gate internal-names	python3 gates/protean-ops/check-internal-names.py .	exit 0 - clean: 46 files scanned, 0 findings
gate op-rotation	python3 scripts/protean-ops/check-rotation.py records/exampl	exit 0 - check-rotation: PASS scanned=2 violations=0 src=records/examples/valid/ROTATION-STATE.md
gate op-inflight	python3 scripts/protean-ops/check-inflight.py records/exampl	exit 0 - check-inflight: PASS scanned=1 violations=0 src=records/examples/valid/INFLIGHT.md
gate op-learnings	python3 scripts/protean-ops/check-learnings.py records/examp	exit 0 - check-learnings: PASS scanned=1 violations=0 src=records/examples/valid/LEARNINGS.md
gate op-hotpath-freeze	python3 scripts/protean-ops/check-hotpath-freeze.py records/	exit 0 - check-hotpath-freeze: PASS files=1 intact=1 changed=0 missing=0
gate op-decision-report	python3 scripts/protean-ops/check-decision-report.py records	exit 0 - check-decision-report: PASS scanned=1 violations=0
test suite	python3 -m unittest discover -s tests	exit 0 - Ran 29 tests in 1.155s / OK
standalone installer	bash install.sh --target <dir> --dry-run	exit 0 - result: dry-run, no files written

Every command above was run in a clean checkout of the tagged commit. Continuous
integration on this pull request is PENDING at the time of writing: this body records only what was
observed locally.

Verification notes

• The leak gate reads SHA-256 digests of private identifiers, not the identifiers
  themselves, so the gate never carries what it detects.
• The bad fixtures in tests/fixtures/ are base64 encoded for the same reason.
• install.sh --dry-run writes no file and creates no directory; the test suite
  asserts both the dry run and a real install.

What this does not do

• No merge, no visibility change, no archive, no transfer. Review and integration
  are separate steps owned by the reviewer.
• No claim is made about behaviour beyond the commands recorded above.

Posted by the build agent; the review and the merge decision are the reviewer's.

License

MIT. The committed LICENSE file is authoritative.