Public production overview of the Talomnia Pitch Deck

Point at a column name, or tap it, and its definition appears here.

Artifact type — The managed knowledge-graph type an artifact belongs to: role, skill, blueprint plus the governance types constraint, success criterion, policy and capability description. The type decides which contract the artifact lives under and how it may be reused.

Artifact version — The version of the knowledge artifact as it took part in this task. Artifacts are versioned in the private knowledge repository and a task is bound to a specific version rather than to «current» — otherwise the evidence would stop reproducing at the next edit.

Artifact source — The artifact's identifier and the link to its Capability Atlas entry where one is published. The source is the address at which the claim can be checked; where no public entry exists the identifier is shown alone rather than an invented link.

Lifecycle status — The stage of a knowledge artifact: draft, reviewed, validated, shared-internal, public-sanitized, deprecated. Only public-sanitized artifacts reach a public surface; the rest are accounted for as withheld rather than quietly omitted.

Disposition — How a knowledge artifact took part in the task: created — authored for the first time, reused — used unchanged, modified — revised. The reuse metric stands on this mark, so it is recorded in the ledger entry rather than inferred afterwards.

Linked task — The identifier of the task in which this artifact was touched. A task is the unit of project work; it contains the subtasks that time and cost are accounted against, and this identifier is what ties a row of evidence to the ledger records.

Point at a column name, or tap it, and its definition appears here.

Subtask — The accounted unit of execution: one step of a task with its own Workflow Ledger record carrying time, cost and validation status. A row of the time-and-cost table is a subtask, not a whole task.

Role — A function and area of responsibility within a specific piece of work — for example Developer, Architect, Reviewer, Tester. A managed type of the knowledge graph: a role carries versions, relations, provenance and evidence.

Wall time — The time from the start of a unit of work to its finish, including waiting, pauses and everything in between. It is the elapsed duration of the execution window, not the amount of work done; across parallel lanes the sum of windows is legitimately larger than the calendar time.

Active time — The time during which work was actually executing, with the waiting and the idle stretches inside the window removed. It is always less than or equal to wall time; the difference between them is waiting, not lost work.

Model cost — The cost of the language-model calls for this unit of work: input and output tokens at the provider's price. Where no metered provider invoice exists for the session, the figure is marked as an estimate and its cost basis is published beside the row.

Compute cost — The cost of machine time outside the model: servers, builds, test runs and other infrastructure spent on this unit of work. A zero here means measured absence of such spend, not absence of measurement.

Human cost — The human time on this unit of work, converted to money at the rate the operator declared. Both the rate and the time itself are reconstructed after the fact from evidence rather than measured while the work ran, so every figure in this column is marked as reconstructed — and a row with no human participation has no human cost at all.

Total cost — The sum of model, compute and human cost for this unit of work. Only what was measured is summed: if nothing in the column was measured the total is not zero — it is unknown, and says so.