Inspect before activation
Model output can be useful without becoming active context.
suggested → inspected → accepted → separately activatedBuild / Contribute
A developer surface should expose structure before asking for trust.
Build 09 begins the public developer center: repository shape, quick-start posture, behavioral examples, licensing status, and project governance are visible even though the authoritative R2 source has not yet been publicly released.
Repository structure
Current R2 working shape.
A licensed release package may expose implementation, tests, decisions, and evidence as separate but connected surfaces according to the applicable evaluation or production agreement. This developer view does not imply unrestricted public source rights.
SIW Release Two · working repositoryLicensed source access pending
packages/siw-domain/Governed object types and shared domain model.packages/siw-schemas/Authoritative schema wiring and validation.packages/siw-hashing/Canonical serialization and SHA-256 support.packages/siw-persistence/Governed persistence boundary and repository abstractions.packages/siw-protection/Protection evaluation for governed progression.packages/siw-receipts/Receipt creation, append-only evidence, and verification.packages/siw-orchestration/Transition services for lifecycle, branch, merge, composition, and later binding flow.siw-app/src/r2/Governed application adapters, routes, state, and UI integration.apps/siw-verifier-cli/Independent verification entry point.tests/Fixtures, unit, integration, negative, and conformance testing.docs/Specifications, decisions, evidence, and release-facing records.Quick Start
Prepare the path now; publish exact commands at R2 freeze.
Build 09 shows the developer journey without fabricating a repository URL or pretending unpublished release scripts are final.
1
Clone the published SIW repository
The canonical GitHub URL appears here only after public source release.
2
Install the frozen release dependencies
The release will publish the lockfile and dependency provenance needed for a reproducible local setup.
3
Run checks before the UI
Type checks, schema validation, unit/integration/negative tests, and conformance evidence should precede any claim that the surface is working correctly.
4
Launch the local reference experience
The quick start will point to the exact application route and explain the difference between historical prototype behavior and current R2 behavior.
5
Verify independently
Use the published verifier and evidence artifacts rather than relying on screenshots or successful UI interaction as proof.
Behavioral examples
Understand the invariant before reading the implementation.
These examples describe the intended governance distinction at a high level. Release-grade code examples will be attached to the actual published interfaces.
Branch without silent merge
An accepted branch finding does not automatically alter the parent inquiry.
branch → finding → accepted ≠ mergedRevalidate before consequence
Prior authorization does not guarantee present standing at the bind boundary.
authorization → changed conditions → revalidation → bind / hold / denyLicense + stewardship
SIW is licensed for bounded integration, not unrestricted reuse.
Genesis AiX intends SIW to be interoperable with advanced AI systems without requiring model developers to surrender control of their models, agents, infrastructure, or product identity. Qualified frontier AI laboratories may seek licenses to integrate SIW as a consequence-admissibility layer within specifically authorized AI products or execution surfaces.
WEBSITE LICENSING STATEMENT
SIW Licensing for Frontier AI Labs
Purpose-specific integration rights with Genesis AiX architectural stewardship preserved.
This website statement describes the Genesis AiX SIW licensing posture; it is not the operative license agreement. Qualified frontier AI laboratories may seek licenses to integrate SIW as a consequence-admissibility layer within specifically authorized AI products or execution surfaces.
- Rights by agreement: depending on the agreement, rights may include source inspection, integration, bounded modification, production deployment, and flexible product branding.
- Not unrestricted open source: source access does not grant the right to use SIW as the foundation for another governance architecture, safety platform, consequence-control system, or competing product.
- Deployment-bounded: each license applies to an expressly identified deployment. Rights granted for one product or execution surface do not automatically extend to another.
- Ownership and provenance: Genesis AiX retains ownership of the SIW architecture and underlying intellectual property. Appropriate architectural provenance, copyright, attribution, and license notices must be preserved even where the implementation is branded primarily under the licensee's own product identity.
Licensing principle: Integrate SIW. Improve it for the licensed implementation. Make it native to your environment. Do not use the source to build something else.
Evaluation, commercial terms, source access, deployment scope, and expanded product-family rights are negotiated separately.
Frontier AI laboratories interested in evaluating or licensing SIW may contact Genesis AiX for a bounded licensing discussion.
Patent filing status
SIW provisional application filed August 16, 2026
SIW is the subject of U.S. Provisional Patent Application No. 64/135,007, filed August 16, 2026.
Systems and Methods for Governed Semantic Inquiry, Context Activation, Selective Merge, Immutable Model Binding, and Verifiable Transition Receipts
This filing reference is provided for provenance and disclosure context. It is not represented here as an issued patent or granted right.
Build / provenance
Inspect status before treating a surface as released implementation.
The current site keeps website implementation status, source-release status and IP filing status separate.