Repository navigation
J3S-AUTHZ-ORACLE-001: executable authorization truth model - #3
Draft
JaeTierce31 wants to merge 9 commits into
Draft
JaeTierce31 wants to merge 9 commits into
JaeTierce31 wants to merge 9 commits into
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
Stacked on
PROP-OPS-AUTHZ-HARDEN-001, this PR introduces one implementation-independent authorization oracle for Property Ops and an adversarial Vitest fixture suite.The oracle encodes DB-derived authority and explicitly proves that client-controlled role/org/property/unit hints cannot change authorization decisions when authoritative actor/resource state is unchanged.
Added
src/security/authz-oracle.tssrc/test/authz-oracle.test.tsdocs/evidence/J3S-AUTHZ-ORACLE-001.mdJ3S-AUTHZ-ORACLE-001 VerificationworkflowInitial executable invariants
Governance state
CANDIDATE / merge-blocked.
This PR does not promote AUTHZ-HARDEN to PASS. It still requires parity adapters that execute the same oracle cases against:
USING+WITH CHECKmutation semantics);/api/property-ops/*surface with real signed identities.The existing signed-token, true two-connection audit-lineage, closed-loop plumbing, observability, PITR, and rollback blockers remain in force.