Architecture
Bounded context. Scoped access. Reviewable change.
A simplified view of how ReasonTrail turns captured project evidence into useful context without handing a model unrestricted system access.
System overview
01Web app · Mac Companion · MCP clients
02Authentication + tenant scope
03Project records + relationships
04Context discovery + retrieval
05Router AI + configured providers
06Review queues + audit events
07PostgreSQL
Data model
A project-centered relationship map.
Organizations define the tenant boundary. Projects connect captured evidence, structured work, context versions, reviews, and controlled Operator events.
OrganizationsMembers + teamsProjectsConversations + capturesTasks + decisionsIdeas + blockersResources + relationsContext versionsReviewsOperator runs + events
Router AI
Providers are configurable boundaries.
Selected project context may be sent to the configured provider. Provider credentials remain server-side and are never exposed to MCP clients.
context.version: versionedtoken_budget: boundedprovider: configureddatabase_credentials: never sentOperator lifecycle
One controlled agent, persisted stages.
Operator v1 supports controlled task-status work and bounded repository inspection. It does not expose arbitrary shell, deployment, browser, or external-system actions.
01Plan↓
02Approve if sensitive↓
03Execute↓
04Verify↓
05Update memory