productoverview

One platform. Three parts.

Xorq records what your agents do as verified, reusable work; runs each piece once; and executes it on whatever engine holds the data. Each part stands on its own. Together they are how a number gets from an agent to a board pack with its proof attached.

Xorq Ledger Business meaning as runnable, approved expressions.

Every question an agent answers becomes a named, versioned entry: the expression, the result, the lineage, and who approved it. The next agent starts from verified work instead of a blank prompt.

structuredexecutablehuman-approvedcompounds

read about xorq ledger →

Xorq Cache Work runs once. Reused, not recomputed.

Results are keyed on the expression and the source versions that produced them. A repeated question replays from the cache; when a source changes, only what depends on it recomputes.

keyed on contentreplayed on hitnever staleno TTL to tune

read about xorq cache →

Xorq Anywhere One expression. Every engine.

Write the definition once. Xorq compiles it to whichever engine holds the data, moves only the aggregates a step needs, and records one entry no matter where it ran.

compile per enginearrow flight transportbulk rows stay putone hash everywhere

read about xorq anywhere →

how they connectone question, start to finish

agent01

Composes a questionOn existing Ledger entries, not raw tables.

expression

xorq anywhere02

Compiles and runs itOn the engine that holds the data. Aggregates move over Arrow.

result

xorq cache03

Stores the resultUnder the expression's hash. Same question later replays.

entry

xorq ledger04

Records the entryLineage, approver, history. Addressable by the next agent.

↺the next question starts from 04