Talomnia is the commercial product layer above Datarim, Arcanada and the Knowledge Contract Architecture. Its first product, Talomnia Workforce, is designed to let a customer order professional work — research, development, architecture review, audit, document analysis — from digital professionals instead of hiring an employee for every such need. The customer describes the task; Talomnia is designed to determine the required Roles, Skills and Blueprints, fix the economics before execution (estimate, Budget Limit, acceptance criteria), execute through AI agents, software or people, and return the result together with the Evidence behind it.
By design, work travels Work Request → Work Order → Work Execution with acceptance and rework built in, and a Knowledge Contract per task states what the performer must know, may do, must not do, and what counts as success. By design, the execution boundary is the customer's repository rather than direct access to their infrastructure. Its status today is building: the technology foundation works, but the business is not yet validated. There is no external paid case, no sustainable B2B revenue and no measured unit economics; the immediate milestone is Evidence Gate 1 — one real external customer submitting a task, paying, receiving the result and accepting the work. Every target in the roadmap is a hypothesis still to be tested, not an achieved result.
- Status
- In development; business not yet validated
- Autonomy (AAL)
- L1 → L4
- Site
- talomnia.com
- First product
- Talomnia Workforce
01
Order work, not hire
By design, a B2B customer orders research, development, architecture review, audit or document analysis from digital professionals instead of hiring an employee for each need; this customer journey is planned and not yet validated.
02
Economics fixed before execution
By design, the estimate, Budget Limit and acceptance criteria are agreed up front, with settlement after acceptance.
03
Evidence with every result
Each deliverable is designed to return with the Evidence behind it, not just an answer.
The gap behind the product
Knowledge is abundant; reliably accessible professional work is still scarce. That gap is the product.
By design, the customer describes the task, and Talomnia determines the required Roles, Skills and Blueprints, then executes through AI agents, software or people.
Capabilities
Status not stated
- Work Request → Work Order → Work Execution with acceptance and rework built in
- Knowledge Contract per task — what the performer must know, may do, must not do, and what counts as success
- Economics fixed before execution — estimate, Budget Limit, acceptance criteria, settlement after acceptance
- Evidence and provenance with every deliverable, not just an answer
- Roles, Skills and Blueprints designed to be reused across tasks and professions
- Client-side execution boundary — the repository is the interface, not direct access to customer infrastructure
Current autonomy level
Weakest link
The technology foundation exists (Datarim as a working multi-agent execution framework, Arcanada as the runtime, Knowledge Contract Architecture as the research core), but Talomnia itself is not yet a validated business: no sustainable B2B revenue, no repeatable acquisition funnel, no validated unit economics, and no external paid case. The immediate ceiling is Evidence Gate 1 — one real external customer submitting a real task, paying, receiving the result and accepting the work.
Roadmap to L4
- Stage 1 — turn the existing foundation into a customer journey: submit a task → understand the cost → pay → receive the work → verify the result. Gate 1 is one real paid external task, accepted.
- Stage 2 — prove it was not a coincidence: different B2B customers, measured acceptance and rework, execution and verification cost, first signal of viable unit economics.
- Stage 3 — prove repeatability: Skills and Blueprints actually reused, less manual setup, lower rework, and a falling Time to Digitize a Profession (TDP).
- Stages 4-5 — early scale, then open the infrastructure layers (Enterprise Capacity, Capability API / A2A, Contributor Network) only after customers pay, return and the economics hold.
Next step
Review the current build and its development plan
BUILDING means active development, not a promise of public availability. Use the current capabilities and roadmap above as the reference.
Review the path to the target level