Product runtime
helix-unified remains the private flagship for Samsarix Social, the Realms application variant, accounts, billing, and durable user data.
Architecture and lifecycle guide
Know what each layer is allowed to own.
Samsarix is a portfolio, not one giant runtime. This guide separates the private flagship, reusable packages, consumer-owned adapters, effect boundaries, public documentation, and preserved experiments so a useful extraction does not become a second source of truth.
01 / System map
Five boundaries keep the portfolio understandable.
The owner of a boundary also owns its authorization, privacy, failures, and compatibility promises.
Reusable primitive
A focused package owns a narrow operation such as typed tool invocation, provider transport, policy evaluation, or payload redaction.
Consumer adapter
The adopting application translates its own identities and data into the package contract and can remove the adapter without rewriting the package.
Effect boundary
The application—not a generic agent loop—owns consequential writes, consent, idempotency, durable queues, and operator recovery.
Evidence boundary
Tests, fixtures, compatibility windows, and release records support only the exact version and workflow they exercised.
02 / Evaluate an agent system
Trace one real workflow before trusting the architecture.
This compact method preserves the strongest reusable material from the earlier private Project Guide.
- Input: identify who supplies the request, context, credentials, and constraints.
- Orchestration: find the state machine, stopping rules, retry limits, and timeout behavior.
- Specialist work: distinguish model suggestions from deterministic validation and application code.
- Policy and effects: locate the final authorization check and every external side effect.
- Record: verify what persists, what is redacted, who can inspect it, and how a failed run resumes.
- Proof: run the smallest end-to-end fixture that exercises success, denial, timeout, and rollback.
03 / Adoption test
Restore a removed relationship only when all five answers are yes.
A roadmap idea or copied implementation is not evidence that a runtime dependency should return.
- A real Social, Realms, companion, or standalone workflow currently needs the behavior.
- The earlier behavior was functional—not mocked, copied, unavailable, or documented only.
- The relationship fits a stable package, HTTP, event, schema, or immutable workflow contract.
- One side explicitly owns compatibility, authorization, privacy, limits, and failure recovery.
- Adoption retires or clearly subordinates a duplicate instead of creating another canonical implementation.
04 / Documentation lifecycle
One public front door, preserved source histories.
Consolidation changes maintenance ownership; it does not silently delete, archive, or relicense a source repository.
Canonical
Samsarix Field Guide
Public repository catalog, portfolio boundaries, current Samsarix coordinates, and cautious lifecycle labels.
Reference source
Project Guide
Private case-study source. Its reusable evaluation method is represented here; its site implementation and AGPL-licensed files are not copied.
Preserved consolidation source
Hub Directory
Public index of bundled profiles and legacy concepts. Historical exports, binaries, integrations, and sensitive-history categories remain outside this site.
Historical hold
Helix
Earlier portfolio source retained for history until a separate security, licensing, and archival decision is approved.
05 / License boundary
Consolidate the guidance, not incompatible source trees.
This page is newly authored within the MPL-2.0 Field Guide. It summarizes reviewed portfolio facts without copying the Project Guide's AGPL implementation, the Hub Directory's BUSL/legacy artifacts, private flagship source, or historical exports.