Memory recall

Conclusions Ask Demiton and your workflows have written back to memory.

Part of Platform in the register catalog.

Register ID

memory_recallUse this name to ask for the register. The API calls it a shelf ID.

Each record is

An eventSomething that happened at a point in time.

Status

AvailableFilled today from connected systems, uploads or public data.

Data

OrganisationPrivate to each organisation's own workspace.

Version

v1Current version.

Download JSON SchemaSee an example record

Connectors

Connected today

Demiton keeps this register current from these systems now.

No system fills this register yet.

On the roadmap

Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.

None planned yet.

Fields

17 fields: 6 required, 11 optional.

Required

Every record carries these fields.

contentText

The durable conclusion: a chat statement, a run narrative, or a report finding.

Example: Emerald Street Rejuvenation is 56.8% complete against a $…

source_systemTextUnit: DEMITON)

None.

Example: DEMITON

source_idText

The producer's identity within the source (workflow_run:{id}, report:{id}, a content hash for chat).

Example: report:9021

occurred_atDate and timeISO 8601, with time zone

When the remembered event happened (the atom's event time).

Example: 2026-06-30T18:00:00

confidenceNumber

Producer's confidence in the statement.

Example: 0.86

subject_entity_idText

The subject the memory is about; today always the org-root Entity for narratives and reports, or the resolved entity/project for chat.

Example: org-root:bridgeworks-group

Optional

Present when the source system records them.

source_typeTextUnit: workflow_run \

report_run \.

workflow_run_idWhole number

The WorkflowRun whose completion produced the narrative or finding.

Example: 9021

workflow_run_nameText

Display name of the producing run.

summary_sourceTextUnit: deterministic fallback)

None.

workflow_nameText

Report workflow name, also embedded in content.

Example: Weekly Project Health Report

domainText

The report's business domain (e.g. finance, operations).

Example: operations

report_typeText

The report class.

Example: weekly_project_review

run_finished_atDate and timeISO 8601, with time zone

When the producing run finished.

Example: 2026-06-30T18:02:00

citationGroup of fields

Provenance leaf (shelf, source kind, origin URI, confidence).

valid_untilDate and timeISO 8601, with time zone

Soft-delete/retirement time; NULL means live.

environmentText

Deployment environment, part of the dedup key.

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

memory_recall.example.json

{
  "confidence": 0.86,
  "content": "Emerald Street Rejuvenation is 56.8% complete against a $2.85M budget, tracking to program with no open safety NCRs in June.",
  "domain": "operations",
  "occurred_at": "2026-06-30T18:00:00",
  "report_type": "weekly_project_review",
  "run_finished_at": "2026-06-30T18:02:00",
  "source_id": "report:9021",
  "source_system": "DEMITON",
  "subject_entity_id": "org-root:bridgeworks-group",
  "workflow_name": "Weekly Project Health Report",
  "workflow_run_id": 9021
}

Use this contract

The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.

Schema URL

https://docs.demiton.io/registers/memory_recall/v1.json

Show the full JSON Schema

Loading the schema…