01
Origin condition
Why it exists
Collaborative systems become unsafe when authority is implied, messages lose provenance, operators cannot freeze drift, and repair is treated as an afterthought. Parallax SOSA exists to make sovereignty executable through explicit authority, signed envelopes, governed bridges, and reversible operation.
Can a distributed runtime remain useful while every consequential action retains a visible source of authority and a path to stop?
02
Working system
What it does
- ✉Moves signed envelopes
Carries identity, mandate, payload, evidence, constraints, expiry, and signatures through the runtime.
- ⚖Executes bounded authority
Operator Authority and Bridge Runner rules determine which actions may cross a boundary.
- ❄Freezes drift
Detects stale mandates, conflicting state, missing receipts, or unauthorized expansion and moves toward a safe frozen state.
03
System anatomy
Architecture
SOSA combines sovereign nodes, Authority Capsules, signed envelopes, Bridge Runner, Operator Authority, Freeze Drift, verification, and repair receipts.
Sovereign node
Local identity, custody, policy, state, and exit behavior.
Signed envelope
Versioned message with mandate, evidence, restrictions, expiry, and signatures.
Bridge Runner
Governed boundary executor that validates and records cross-node action.
Freeze and repair
Stops uncertain operation, preserves state, and requires explicit recovery authority.
04
Present tense
Current state
Parallax SOSA is recorded as Active at the Growing stage. The inventory currently marks 4 artifact lanes Ready, 3 Partial, and 1 Missing.
B3 Tier 1 room draft · Core canon · Operational evidence · public candidate
05
Honest edges
Known limitations
- The architecture is active but not represented as a formally verified secure operating system.
- Cryptographic signatures are only as trustworthy as identity proofing and key custody.
- Operator authority can still be abused if governance and review are weak.
- Distributed failure, clock drift, replay, partition, and recovery behavior require deeper implementation testing.
06
Claim boundary · v1.1.0
What we are—and are not—saying
SOSA v1.2 is frozen as a final baseline and v1.3 alpha includes Bridge Runner, Operator Authority, Signed Envelopes, and Freeze Drift work.
SOSA is not certified security software, a legal sovereignty mechanism, a guarantee against unauthorized action, or proof of fault tolerance beyond tested implementations.
07
Development memory
Ledger
B3-SOSA-001-01Parallax SOSA v1.2 frozen as the final baseline.
✓ AcceptedB3-SOSA-001-02v1.3 alpha introduced Bridge Runner, Operator Authority, Signed Envelopes, and Freeze Drift.
✓ ActiveB3-SOSA-001-03Tier 1 sovereign-runtime room drafted with implementation limits.
✓ DraftCurated project receipts · source-file binding and human review remain pending
08
Directional, revisable
Roadmap
Publish one signed-envelope walkthrough
Show mandate, validation, execution, rejection, freeze, and repair in a compact example.
Implement adversarial tests
Exercise replay, stale authority, partial failure, conflicting commands, and recovery.
Formalize critical invariants
Apply stronger verification only to the bounded safety properties the runtime can actually enforce.
10
B10 evidence trail
Featured evidence
Direct original-source trail
B11 adds README-verified public repositories, live experiences, publications, or creator channels. These establish source availability without proving every project claim.
Flow Covenant Runtime — Live App
Public stable interactive release with facilitator mode, guided mode, governance gates, repair tools, and local receipt export.
Open bound artifactFlow Covenant Runtime — Public Repository
Public-safe, local-first governance workbench built around invitation, consent, alignment, receipts, repair, and renewal.
Open bound artifactGovernance Drift in AI-Assisted Workflows — DOI
Working paper and proposed framework. The source explicitly states that no empirical validation or certification is claimed.
Open bound artifactGovernance Drift / RSDC — Public Repository
Claim-disciplined framework for detecting governance drift through role separation, append-only receipts, adversarial review, operator approval, and release gates.
Open bound artifactParallax SOSA — Project Field Card
B4-generated visual identity card built directly from the reviewed constellation registry.
Open bound artifactM
B11 original media
Open the original trail
Public governance-runtime and governance-drift sources adjacent to the SOSA architecture.
Flow Covenant Runtime — Public Repository
Public-safe, local-first governance workbench built around invitation, consent, alignment, receipts, repair, and renewal.
Open original sourceGitHub · MichaelWave369/flow-covenant-runtime · README verified 2026-07-25Flow Covenant Runtime — Live App
Public stable interactive release with facilitator mode, guided mode, governance gates, repair tools, and local receipt export.
Open original sourceGitHub Pages stable live app · README verified 2026-07-25Governance Drift / RSDC — Public Repository
Claim-disciplined framework for detecting governance drift through role separation, append-only receipts, adversarial review, operator approval, and release gates.
Open original sourceGitHub · MichaelWave369/governance-drift-rsdc · README verified 2026-07-25Governance Drift in AI-Assisted Workflows — DOI
Working paper and proposed framework. The source explicitly states that no empirical validation or certification is claimed.
Open original sourceZenodo DOI 10.5281/zenodo.20466412 · repository README verified 2026-07-2511
Publication intake
Artifacts & sources
Parallax SOSA v1.2 final
Frozen sovereign-runtime baseline.
View archive recordarchive:intake/sosa-v12Parallax SOSA v1.3 alpha
Bridge Runner, Operator Authority, Signed Envelopes, and Freeze Drift work.
View archive recordarchive:intake/sosa-v13-alphaSigned-envelope walkthrough
Required human-readable architecture proof.
View archive recordarchive:intake/sosa-envelope-walkthroughSource basis
archive:intake/parallax-sosa/source-basisinternal-prototypeportal:project/parallax-sosa@v0.4-b3planning-inventoryReview: Canon, claims, privacy, accessibility, and publication review · pending
12
Move with evidence
Next actions
The system should be judged by authority, refusal, freeze, and repair—not only successful execution.
reviewReview the artifact registerSee which source packages, visuals, demonstrations, and public links are actually ready.
secondaryTrace related projectsFollow documented dependencies and neighboring systems without inventing connections.