Versioned product truth
No roadmap item gets to pretend it shipped.
This page is generated from three repository contracts. Support, distribution and entrypoint claims cannot be edited here independently.
Release channel
Not published
The source repository, deterministic artifacts and lifecycle candidates exist. npm scope ownership and trusted publishing still require external registry authority.
data safety source candidate
data safety published byte replay
private multi app dogfood accepted
canonical repository control verified
public source launch authorized
npm scope control verified
trusted publishing configured
tag protection configured
license and third party notice closure verified
candidate targets clean room certified
First release boundary
7 public packages
@tasq/schema@tasq/core@tasq/cli@tasq/mcp@tasq/extension-sdk@tasq/protocol-adapters@tasq/console
Surfaces
Every way in.
Every boundary visible.
Agents consume machine contracts. Humans use CLI, projections and Console. Remote consumers have no supported path until Server exists.
| Surface | Status | Transport | Entrypoint | Writes |
|---|---|---|---|---|
| Cli Json | Certified | local process | tasq onboard --space <id> --actor <label> --json | yes |
| Mcp Stdio | Local only | stdio | tasq mcp --tenant <id> --actor <label> --capabilities <set> | yes |
| Embedded Typescript | Integration | in process | @tasq/core | yes |
| Local Console | Local only | loopback http | tasq web --tenant <id>; tasq web status --tenant <id> --json | no |
| Markdown Projection | Local only | filesystem projection | tasq projection | no |
| Extension Sdk | Integration | in process | @tasq/extension-sdk | no |
| Protocol Adapters | Integration | in process | @tasq/protocol-adapters | yes |
| Reference Connectors | Reference | in process https adapter | @tasq-internal/reference-connectors | yes |
| Replication Kernel | Integration | integrator supplied | @tasq/core replication APIs | yes |
| Public Site | Certified | public https static files | https://tasq.run; https://tasq.run/product-truth.json; https://tasq.run/adopt.json | no |
| Rest | Integration | host integrated fetch request response | @tasq-internal/server createHostedReadHandler; createHostedHttpHandler | yes |
| Remote Mcp | Not built | streamable http | none | no |
| Hosted Console | Not built | https bff | none | no |
Repository contracts
Trace every displayed claim.
docs/concepts/PRODUCT_SURFACE_MATRIX.jsontasq.product-surface-matrix.v1sha256:27793b8052465b44b0b9f1651925d144b11cf7e9c53ecc24eafd528a30e90394docs/roadmap/BACKLOG.jsontasq.backlog.v1sha256:adb8c336b0bfe921462732890893836d6c5d79b981d9fd8d4c18fad56bf04de2docs/releases/PUBLIC_RELEASE_POLICY.jsontasq.public-release-policy.v1sha256:eb8fc7985634226cac8fb90f83681cd2670dbd30f50042e3ff26b79e71da1d30
Need the reasoning behind these boundaries?
Read the product architecture before choosing an integration path.