Architecture
One system.
From data to action.
Application data, maintained views, and authorized actions connect through one history. Agent work and human reviews remain available for later tasks.
Explore the systemFollow the data.
Application data
Reads, synchronization, and direct writes
Recorded history
Source, time, and order
Queryable state
Records and views for agents and products
Reads, synchronization, and direct writes contribute to the same history.
Data modelAction request
The requested operation and its inputs
Authorization
Permission to perform the requested action
Managed execution
Configured code acts on the external system
Requests, attempts, and results remain separate.
Execution modelRetained inputs
Original records and recorded outputs
Projection rules
The same computation over the same inputs
Reconstructed state
A view reproduced from its recorded history
Rebuilds reuse recorded results without repeating inference or external actions.
Reconstruction modelData acquisition.
Read authorized application data or use retained data under freshness rules. Synchronization maintains selected datasets between tasks. Direct writes add generated work and human decisions to the same history.
Ordered history.
The event log stores immutable records with an ID, source, recording time, and JSON payload. IDs determine append order. Each observation retains the data returned by its source.
Read the event formatQueryable views.
A projection maintains records or views from recorded data. Developers define its inputs, computation, and output. Agents and product interfaces query those views for current records and related context.
Try an account view
Account 4821
Illustrative records computed in this page. Append an older observation, or clear the view and apply its recorded inputs one at a time.
CRM account observations
- Event #201Source revision 12 · weekly notifications
- Event #209Source revision 13 · monthly notifications
Maintained view
- Frequency
- Monthly
- Source revision
- 13
- Supporting event
- #209
The view reflects source revision 13. Recorded history retains both observations.
9 retained records · 1 recorded draft · 1 recorded execution attempt
Authorized actions.
An agent records a request. Groundhog checks authorization, runs the configured executor, and retains each attempt and result. A subsequent application observation can confirm the resulting state.
Compare execution outcomes
Each case starts with weekly notifications at source revision 12.
- Action request
- Monthly notifications
- Authorization
- Permitted
- Execution attempt
- One recorded attempt
- Execution response
- Accepted
- Source observation
- Monthly notifications, revision 13
The response is accepted. A subsequent CRM observation confirms monthly notifications.
Retained history.
Generated work, human reviews, and action outcomes remain connected to the original data. Later tasks retrieve it as context. Rebuilds reuse recorded inputs and results without repeating inference or external actions.
Object storage holds the event log and projections. Memory and SSD caches serve frequent reads.
The event log.
The Rust HTTP service supports durable append, retrieval by ID, and ordered reads. Synchronization, projections, authorization, and managed execution describe the broader product architecture.