Product
MOD-05 · Memory and records
Behavior and limits for memory and records, based on the reviewed product catalog.
FEAT-016 · Handoff and recall
Context is triaged as critical, important or summarizable. Recall resolves pointers when needed; it does not reload the entire conversation.
FEAT-017 · OrkMind memory
The project tenant receives decisions, handoffs and lessons according to permissions. Unavailability degrades to files with an explicit event; it does not silently use another database.
In version 0.6.10, the DSN can come from a file in ork’s secrets folder, at ~/.orkastery/segredos/, declared by memory.database_url_file (0600 or 0400, a single line), instead of an environment variable visible to agents; memory.database_url_env is still accepted, and the two sources are exclusive. A missing, insecure or invalid file degrades to files with dsn.arquivo-ausente, dsn.arquivo-inseguro or dsn.arquivo-invalido, without falling back to another database, and a child process answer that repeats the DSN or its password is rejected whole, with memory.transport.secret, brain.transport.secret or brain.migration.secret.
Search by meaning is separate from tag search: a local derived vector index, results from a single tenant marked as non-deterministic, and nothing entering the prompt on its own. Vectors from different models or dimensions are never compared, and unavailable embeddings have an embeddings.* reason without bringing down the regime.
Search by meaning was released in version 0.5.0 and turns off with memory.embedding.provider: none.
FEAT-018 · Documentation as code
Frontmatter and links are checked against code and Git. Synchronization does not automatically turn a plan into deployment or availability.
Parity works both ways: codigo: Mesclado requires the commit on the base, and the item thread’s ship(<thread>) merge requires codigo: Mesclado (docs.paridade.merge); the generated index must match the frontmatter (docs.paridade.indice). A push to main fails on either divergence; in a pull request they only warn, and ork docs sincronizar --escrever fixes them.
FEAT-019 · Ledger telemetry
Metrics declare time range, provenance and coverage. Estimates require a method, assumptions and author; they are not presented as measured hours or spending.
FEAT-024 · Company Brain in the CLI
ork brain context returns ork.brain-context/v1 with pedido, itens, lacunas and a canonical JSON digest. It includes requested entities and their parents; without --ids it uses the scope bound by ork brain bind. Every item carries source_ref, source_hash, source_version and location, plus freshness against the canonical portfolio.
Incomplete citations become citacao.incompleta gaps. ACL-withheld items expose only their ID and retido freshness, never content recovered from the local source. An unavailable or refusing Brain does not produce a package fabricated from local files. Identity comes from authenticated transport; reads do not write, and writes require accepted activation and a database grant.
The package comes from OrkMind’s context mode and the core checks it: schema, tenant, request, digest, citation, order, parent closure and the target of each id. A package that does not check out ends with brain.context.server-invalid, without falling back to querying; only brain.selection.context-unsupported, from an OrkMind older than the mode, makes the core build the same package with query and get. The caminho field says which path was used, and both paths give the same digest for the same data.
ork brain context --thread <thread> --ids <ids>FEAT-028 · Learning across threads
Lessons from closed threads feed GOAL and PLAN for the same product. Repeated failures propose policies; a proposal does not activate a block on its own.
The claims.failed lesson becomes the opt-in policy claim_sem_prova_local, off by default: when declared, ork claims add runs the claim command once, within the verify timeout, and only warns with policy_warn; the claim is recorded either way.
FEAT-033 · Decision dossier
ork brain dossie gathers a thread’s decisions with the goal, project and citable context, including recorded options, who decided and the evidence. Each decision carries the ledger line citation and the IDs that Company Brain assigns to the fact. Read-only, also available as ork_brain_dossie in MCP and OpenClaw.
The owner’s answer appears only when the ingress receipt checks out; otherwise it becomes the resposta.sem-prova gap. A report about the owner without a receipt never becomes a decision. Informed decisions do not store options and show the alternativas.nao-registradas gap; facts withheld by ACL expose only their ID and retido freshness.
The dossier is on main and was released in version 0.5.0.
ork brain dossie --thread <thread>
ork brain dossie --thread <thread> --decisao <id>FEAT-038 · Written knowledge
ork conhecimento lists, shows and checks the company’s written documents (policy, specification, guide) in the folder declared in orkastery.yaml, with each one’s version (sha256) and source (file); whatever does not check out arrives as a typed gap. The four queries have the same names in MCP, in the OpenClaw plugin and in Hermes, and the answer follows the ork.conhecimento/v1 contract.
Each document is Markdown with frontmatter: id, titulo, colecoes and, optionally, referencias. A cited decision is checked in the ledger, and a Company Brain ID is checked with get, which requires memory.mode: orkmind; without the conhecimento block in the manifest, a query answers with the conhecimento.nao-declarado gap. All three slices were released in version 0.6.0.
ork conhecimento listar --colecao <colecao>
ork conhecimento mostrar <doc-id>
ork conhecimento colecoes
ork conhecimento verificar