Public preview
Front door, SIW homepage, Governance, Architecture, Roadmap, Library shell, Research, and selected proof routes.
Current / In progress / Planned
Release Two is moving from progression to convergence.
This page is intentionally status-forward. It should always distinguish accepted implementation from active work, planned release packaging, and future research.
Accepted
Governed foundation
Domain objects, schemas, hashing, persistence, lifecycle transitions, and receipts.
Accepted
Governed progression through branch-finding acceptance
Protection, activation, bounded branches, findings, inspect / accept / reject, standing revalidation, and provenance preservation.
In progress
Controlled convergence
Selective merge proposal and governed merge application, without treating proposal or prior acceptance as merge authority.
Next
Composition, binding, verification, authority, hardening
The remaining consequential arc before R2 closure.
Launch
Coordinated licensed source release
Code, architecture, evidence, documentation, licensed source access, project governance, and a hosted reference experience may be released under the applicable bounded evaluation or production terms after release freeze and IP/license review.
Public website phases
The website leads the source release.
Marketplace visibility can begin before R2 closes without presenting unfinished software as available.
Knowledge Explorer
Tree + sidebar MVP first; map, lineage, evidence, chronology, and audited 3D integration follow.
Licensed source / evaluation launch
Final quickstart, source-access package, examples, release evidence, licensing posture, contribution model, and release tags, with rights bounded by the applicable agreement.
Current release standing
Where SIW is now — and what comes next.
This release surface distinguishes accepted engineering, working representation, review standing, Release Three planning, and longer-range architectural direction. Status labels report standing; they do not create authority.
Accepted
Implemented
Working Prototype
In Review
Planning
Proposed
Deferred
Not Authorized
See the full SIW Evolution / chronology (Stage 01 → 02 → 03) →
| Architecture / capability | Release Two | Release Three planning | Future direction | Current classification |
|---|---|---|---|---|
| Governed object model | Accepted implementation basis. | Extension as required by accepted future architecture. | Provider-neutral governed participation. | Accepted |
| Inquiry / context lifecycle | Accepted basis with working interactive representation. | Deeper runtime and execution integration. | Federated context and capability participation. | Implemented / In Review |
| Branch / merge lifecycle | Accepted implementation basis; advanced controls represented in Expert mode. | Runtime refinement. | Governed cross-capability return paths. | Accepted |
| Protection and current standing | Accepted implementation basis. | Expanded runtime application. | Capability and provider standing federation. | Accepted |
| Stage / STALE workflow | Working representation in Team Review Candidate 1. | Candidate bind/runtime integration. | Whole-assembly standing across context and capabilities. | In Review |
| Guided / Standard / Expert | Working progressive-disclosure interface. | Candidate profile-backed persistence. | Adaptive guidance without governance bypass. | In Review |
| SIW Profile | Not implemented in Team Review Candidate 1. | Planning: experience level, preferences, guide settings, permissions, bounded usage signals. | Governed user preference surface across SIW services. | Planning |
| Guide Cards / adaptive guidance | Not implemented. | Candidate direction following Profile architecture. | User-controlled adaptive assistance. | Proposed |
| Governed Skills | Not implemented as a Release Two capability class. | Candidate architecture: discover, inspect, accept, protect and explicitly activate. | Provider-neutral governed capability assembly. | Proposed |
| MCP / external tools | Not implemented in Team Review Candidate 1. | Design candidate where supported. | Governed discovery and invocation through capability federation. | Proposed |
| Genesis API Middleware / Model Gateway | Core SIW operational integration architecture. Live model invocation is not yet connected in Team Review Candidate 1. | Provider-neutral runtime integration can deepen without changing SIW governance semantics. | Common governed boundary across frontier, open-weight, enterprise, private, and specialized knowledge environments. | Core Architecture / Integration Pending |
| Governed Model Federation | External intelligence connectivity is fundamental to SIW; multi-provider federation is not yet implemented in the current team-review application. | Candidate model selection, routing, comparison, provider standing, disclosure control, and return provenance. | OpenAI, Anthropic, Google, xAI, open-weight, enterprise/private models, and specialized knowledge environments through a common governed gateway. | Planning / Integration |
| Tools / plugins / apps | Not implemented as a Release Two capability federation. | Candidate capability integration following governed Skills and supported protocols. | External capabilities participate through Governed Capability Federation, separately from model federation. | Proposed |
| Profile and data permissions | Current architecture-definition track. | Candidate runtime enforcement of disclosure boundaries. | Purpose-, provider-, capability- and field-specific controls. | Planning |
| Capability–data dependency notices | Future design requirement. | Candidate disclosure of known functionality consequences. | Changed provider requirements trigger new authorization. | Proposed |
| Genesis Privacy Relay | Not a Release Two requirement. | Not a Release Three dependency. | Optional provider-facing privacy enhancement; not a consumer VPN service. | Future Direction |
| Final public SIW representation | Public switchover not authorized. | Dependent on future accepted standing. | Unified Genesis experience with separate operational boundary. | Not Authorized |
Release progression
Interaction prototype to governed capability federation.
The progression separates historical reference, current Release Two work, Release Three planning, and longer-range architectural direction.
Generation 0 Prototype
Preserved interaction reference and lineage surface. It does not define current Release Two engineering standing.
SIW Release Two
Governed objects, lifecycle, context activation, protection and standing, branch/merge behavior, receipts, staged inquiry inspection and Team Review Candidate 1.
Release Three
Candidate direction includes persistent Profile architecture, deeper runtime/provider integration, Guide Cards and execution-boundary evolution.
Post–Release Three
Governed Skills, MCP/tools, provider capabilities, plugins/apps, capability federation, advanced data controls and optional Privacy Relay.
Operational connectivity architecture
SIW governs the path to external intelligence.
Model connectivity is fundamental SIW operational architecture. Skills, Model Context Protocol (MCP), tools, plugins, and applications are a separate capability layer and must not be conflated with the model gateway.
User / Workspace
Inquiry intent
→
SIW Inquiry Assembly
Context · standing · disclosure
→
Genesis API Middleware / Model Gateway
Provider-neutral governed boundary
→
Selected Model / Knowledge Environment
Frontier · enterprise · private · specialized
→
Governed Return
Provider identity · provenance · evidence · standing
Separate capability path:
Governed Skills → MCP / tools / plugins / apps →
effect-boundary authorization.
Future architecture
Govern more capability without surrendering authority.
These are design directions, not Release Two implementation claims. A roadmap entry does not become authoritative merely by appearing here.
SIW Profile
User-selected experience level, preferences, Guide Cards, data permissions, capability availability and bounded adaptive-guidance signals.
Governed Skills
Reusable procedural capabilities become governed inquiry ingredients rather than silently loaded instructions.
MCP / External Tools
Tool and capability discovery may use supported protocols while remaining subject to Genesis standing and authorization.
Genesis API Middleware / Model Gateway
The provider-neutral operational boundary between SIW and external intelligence or knowledge environments. It governs what may leave SIW, which candidate destination receives it, and how returned material re-enters the governed workspace.
Governed Model Federation
Frontier, open-weight, enterprise, private, and specialized models may participate behind a common Genesis gateway. Selecting a model identifies a candidate destination; it does not itself authorize disclosure or consequential action.
Governed Capability Federation
Skills, tools, plugins, apps, APIs and enterprise capabilities may be discoverable without becoming automatically activated.
Data Permissions
Personal and workspace data cross provider boundaries only for declared purposes and under applicable current permission.
Capability–Data Dependencies
Known functionality consequences of withholding requested data should be visible before the user makes an allow/deny decision.
Genesis Privacy Relay
Optional lightweight provider-facing routing may reduce unnecessary network-identity exposure without becoming a consumer VPN service.
Authority Remains Separate
Profile preference, capability discovery, provider availability, connection state and data possession do not themselves confer runtime authority.
Evidence & provenance
Current Release Two review basis.
The operational application remains separate from this Genesis AiX information surface.
Accepted Release Two engineering head
226c99cc6f6d7533466789d3feb81155c446f7f8
Team Review Candidate 1 source identity
8396823adb4a818330930f9109d7125510561db6fbb5b25373fc93dcef47cf3c
Frozen review candidate
SIW_R2_WORKING_PROTOTYPE_TEAM_REVIEW_CANDIDATE_1_20260824-012145
Frozen ZIP SHA-256
dd42529cec8df3519e3f8f2347d9bf0623aae5a0b344c3b187f75b91e410d277
Operational workspace
Launch SIW
Genesis AiX explains SIW architecture, standing, releases, evidence and future direction. The separately hosted SIW application is the operational workspace.
Team Review Candidate 1 is frozen and its separately hosted review application is now bound to Launch SIW for bounded team review. Public switchover is not authorized.