01Stage 01 / orientationRead the public narrative before the platform details
Start with the overview and philosophy pages to understand why Tellom favors deterministic control, bounded recovery, and explicit trust boundaries.
TellomSite journey
A staged way to read Tellom, from public narrative to protected control.
The site is now easier to navigate as a sequence. Each stage adds context instead of repeating it, and each page deepens the operational story without exposing protected runtime details.
Reading sequence
The journey is designed as an editorial path.
Start broad, then move into system structure, then into control, and then into the protected surfaces where execution and authority live.
02Stage 02 / structureMove through the platform and runtime model
Platform, runtime, and architecture explain how the system stays explainable, replay-safe, and capable without collapsing into feature sprawl.
03Stage 03 / controlReview governance, observability, and security together
These pages show how policy, verification, and operational intelligence stay connected to the same trust contract.
04Stage 04 / continuityFollow recovery and loss prevention
Recovery and continuity content shows how Tellom handles degraded conditions without widening the blast radius or obscuring evidence.
05Stage 05 / protected entryStep from public narrative into protected surfaces
The login path and protected workspaces keep operator and governance access separate while preserving the same disciplined visual language.
System atlas
The site is grounded in an explicit local-first stack.
The docs describe a FastAPI backend, PostgreSQL durable truth, Redis live-state and event runtime, and a Next.js frontend running loopback-first before public exposure.
Tellom stack
The public site explains the system from browser surface down to durable state.
SurfaceNext.js frontend
Public pages, protected login, and routing stay in the browser-facing layer.
APIFastAPI backend
Health, auth, tenant boundaries, and operational APIs remain separate from the public site.
TruthPostgreSQL
Durable truth anchors campaigns, calls, governance, and audit state.
LiveRedis
Live state, queue runtime, SSE delivery, and Streams power runtime and realtime behavior.
Public doc anchors
The journey page mirrors the project’s own documentation phases.
PlanSurface separation
Public, ops, admin, and API hosts each have a single responsibility.
PlanRealtime architecture
Org-scoped events, SSE delivery, and Redis Streams are part of the runtime story.
PlanLoss prevention
Recovery, consistency, and reconciliation are written as deterministic contracts.
Audience map
Different readers can enter at different layers of the same story.
The journey page is meant to be the site’s content-rich doorway: it explains which pages matter for which kind of reader without flattening the system.
Read nextPlatform
See the system model, public/protected boundaries, and the operational contract behind the surface.
Read nextRuntimeFollow replay-safe orchestration, deterministic sequencing, and capability-aware transitions.
Read nextGovernanceReview how policy, approval, and verification constrain execution before state changes happen.
Read nextSecurityInspect the trust, exposure, and isolation model that keeps protected surfaces separated.
Reader groups
The public narrative works for multiple audiences.
Operators, administrators, reviewers, and technical evaluators each need a different amount of context, but the same trust model ties the pages together.
Use the journey and runtime pages to understand how Tellom turns operational clarity into controlled action.
Use governance, security, and architecture to see how authority, scope, and recovery boundaries are kept explicit.
Use the platform, observability, and recovery pages to trace the product logic from design intent to operational confidence.
Use the architecture and philosophy pages to inspect the constraints that keep the runtime coherent as it evolves.
Surface map
Public, operator, and admin surfaces stay editorially aligned.
The site now gives a clearer bridge between public explanation and protected access without collapsing the boundaries between them.
01Public surfacePublic pages explain the control model
The public site is intentionally readable: it shows why Tellom values governance, recovery, and operational trust without exposing private runtime edges.
02Operator surfaceOperator pages stay scoped and action-oriented
Operator pages are built to keep routing, reporting, and replay-aware workflows compact while preserving separation from governance authority.
03Governance surfaceGovernance pages stay deliberate and guarded
Governance pages focus on access, readiness, and platform health so governance remains clear and bounded.
Operational sequence
The platform’s structure becomes easier to scan when read in order.
This sequence shows how the site can be approached as a multi-stage narrative rather than a single explanatory page.
Public reading flow
A new reader can progress from explanation to detail without losing the operational thread.
01Overview
Begin with the homepage to understand what Tellom is and why it exists.
02Depth
Move into platform and runtime to see how the control model works.
03Trust
Read governance, observability, and security to understand how the platform stays bounded.
04Continuity
Use recovery, architecture, and philosophy to see how the system resists loss and ambiguity.
Next-step logic
The journey page also points toward the pages that deepen the platform story.
NextPlatform and runtime
Foundation pages explain the control model and execution semantics.
NextGovernance and security
Trust pages explain policy, boundaries, and protected surfaces.
NextRecovery and philosophy
Continuity pages explain loss prevention, resilience, and operating doctrine.
Navigation
Use the journey page as the entry map.
It is designed to make the rest of the public site feel staged, sequential, and easier to digest.
Platform overviewOperational clarityUnified service posture, tenant lifecycle visibility, and guided operational workflows.Observability overviewReliability insightLive health signals, trend analysis, and clear escalation paths for service continuity.Security overviewTrust and governanceControlled access, policy visibility, and audit-first operational accountability.