Memory recall
Memory recall is one of Demiton's published registers for Australian civil construction. Conclusions Ask Demiton and your workflows have written back to memory. Demiton keeps it current from the systems a contractor already runs and publishes the record's shape as a versioned JSON Schema, so the same question works whichever system produced the record.
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
- v1 (1.0.3)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- Privacy Act 1988Privacy Act 1988 - Australian Privacy Principles
- GDPRGeneral Data Protection Regulation
- Privacy Act 2020 (NZ)Privacy Act 2020 - Information Privacy Principles
- UK GDPRUK General Data Protection Regulation with Data Protection Act 2018
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
14 fields: 4 required, 10 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 $…- confidenceNumber
Producer's confidence in the statement.
Example:
0.86- occurred_atDate and time
When the remembered event happened (the atom's event time).
Example:
2026-06-30T18:00:00- 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.
- domainText
The report's business domain (e.g.
finance,operations).Example:
operations- citationGroup of fields
Provenance leaf (shelf, source kind, origin URI, confidence).
- report_typeText
The report class.
Example:
weekly_project_review- source_typeText
report_run\.- valid_untilDate and time
Soft-delete/retirement time;
NULLmeans live.- workflow_nameText
Report workflow name, also embedded in
content.Example:
Weekly Project Health Report- summary_sourceText
None.
- run_finished_atDate and time
When the producing run finished.
Example:
2026-06-30T18:02:00- workflow_run_idWhole number
The
WorkflowRunwhose completion produced the narrative or finding.Example:
9021- workflow_run_nameText
Display name of the producing run.
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "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.
https://docs.demiton.io/registers/memory_recall/v1.jsonShow the full JSON Schema
Loading the schema…
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would fill from them, on your data, in a 30-minute call.