Bounded by design.
A named collaborator. A selected private repository. An explicit policy. Enforcement stays within the authority you approve.
GITHUB ACCESS. CONTINUOUSLY ACCOUNTABLE.
Access should end.
Proof should remain.
Give temporary access a definitive ending.
Set the policy. Check what changed. Keep the evidence.
POLICY / 01
EVIDENCE / 03
INDEPENDENT VERIFICATION
SCOPED AUTHORITY → CHECKED OUTCOME
✓
RESULT CHECKEDEvidence, not assumption.
↗A HIGHER STANDARD FOR ACCESSExplicit authority✦Independent readback✦Inspectable evidence
01 / THE PLATFORM
The engagement ends.
The access shouldn’t linger.
Contractors move on. Projects close. Permissions stay behind. AccessProof turns temporary GitHub access into a policy you can follow—and an outcome you can inspect.
PRIVATE REPOSITORY
ILLUSTRATIVE DATAAccess with an ending.
EXPIRY POLICY1 collaborator
CHECK CADENCE15 minutes
ASSURANCERead back independently
COLLABORATORACCESS WINDOWOUTCOME
JLjordan.contractorplatform / private-apiEngagement completePolicy expiry reached✓ Independently checked
OUTCOME TRACEEXAMPLE
01Policy due→02Scoped operation→03Separate readback→✓Evidence recorded
Signed record · declared repository scope
01 Put an end date on access.
02 Keep checking after the deadline.
03 Distinguish verified from unknown.
02 / THE PROOF PRINCIPLE
A successful request
is only the beginning.
One system asks for a change. A separately scoped reader checks the result. AccessProof keeps that distinction visible from policy to evidence.
A second look matters.
Fresh inventory and permission readback determine the outcome. A write acknowledgement alone never earns a verified result.
The story keeps going.
Scheduled checks surface overdue access, returned access, and gaps in visibility. Changed findings create a trace you can follow.
03 / TWO PATHS. ONE ACCOUNTABLE OUTCOME.
Separation
is a strength.
Execution and verification have different jobs. They should have different authority.
01
Define the boundaryChoose the repository, collaborator, expiry, and supported enforcement policy.
02
Execute within scopeThe bounded executor uses an authorized operation. Uncertain writes are held rather than blindly repeated.
03
Establish the outcomeThe reader checks fresh provider-reported permissions. Evidence carries the scope, result, and limits.
ACCESSPROOF / CONTROL PLANE01—03
CUSTOMER AUTHORITYExplicit expiry policy
ExecutorBounded operation
ReaderIndependent readback
SIGNED EVIDENCE RECORDWhat actually changed?
VERIFIED◌ UNRESOLVED
Unknown stays unknown. No manufactured green checks.
04 / EXPERIENCE THE DIFFERENCE
Watch the outcome.
Not just the operation.
An interactive, fictional demonstration of the verification model. No real accounts, repositories, or permissions are changed.
CHOOSE A SCENARIOBrowser-only demonstration · no GitHub connection
VERIFICATION TRACEREADY
READY TO INSPECT
Let the evidence decide.
Select a scenario and run the check.
05 / TRUST, WITH RECEIPTS
Earned in the details.
Confidence comes from declared boundaries, observable behavior, and honest limits.
Read about current availability ↗01Separate execution and reading
Distinct GitHub Apps, with scoped responsibilities.
02Signed, inspectable records
Integrity after collection. Provider-reported permissions, not a login test.
03Conservative recovery
Ambiguous outcomes do not trigger blind write retries.
04Control stays with the owner
Explicit policy approval and self-service stop controls.
CURRENT AVAILABILITY
Built to be exact.
Including about readiness.
SERVICE IN VALIDATION
AccessProof is being validated for outside collaborators on a selected private GitHub repository. Scheduled read-only checks are running in a controlled environment. Customer onboarding is not yet open; live GitHub removals remain disabled.
Pricing & availabilityPricing will be announced when customer access opens. Payments are currently test-only; no live subscription is available here.
Declared limitsPolling is not real-time prevention. Team and organization changes, invitations, downloaded copies, and other identities are outside the current scope.
What remains before a customer launch? +
Before customer onboarding opens, we are validating enforcement and recovery, independent security review, performance, and production billing. The walkthrough above illustrates the approach and does not change real GitHub access.
A HIGHER STANDARD STARTS WITH PROOF.
Make access
accountable.
AP