Documentation mapping to schema
Reports and forms contain useful facts, but people repeatedly transcribe them before another system can use them.
How this work runs.
The scattered mark is the problem the run starts from. Every tool sits off the route it drives, glyph and name, and opens its own page. A diamond is a decision the work cannot pass without today, with no tool yet doing it. The accented mark near the end is the named solution, into Solutions; the line beneath it is the outcome the run closes on.
Source documents are profiled, rendered against the target schema, criticised, and corrected by the operator, whose corrections return as learning.
Each step in the order it runs, and where one stops before the next begins.
- 01RECORDSOURCE DOCUMENTS A record the run reads, writes or hands on.Nothing in this run reaches it. Hands on to SCRIBE.
- 02SUBSTRATE · toolMANIFOLD Routes the model calls Scribe makes.Nothing in this run reaches it. Hands on to SCRIBE.
- 03RUN · toolSCRIBE Runs the whole loop: profiles, proposes, checks and renders.Reached from SOURCE DOCUMENTS, NOT MECHANISED YET, MANIFOLD. Hands on to SCHEMA-CONFORMING RECORDS.
- 04RECORDSCHEMA-CONFORMING RECORDS A record the run reads, writes or hands on.Reached from SCRIBE. Hands on to OPERATOR.
- 05RECORD · personOPERATOR The run passes through a person here, not around them.Reached from SCHEMA-CONFORMING RECORDS. Hands on to NOT MECHANISED YET.
- 06RECORDNOT MECHANISED YET A record the run reads, writes or hands on.Reached from OPERATOR. Hands on to SCRIBE.
- 01picked upSCRIBE SOURCE DOCUMENTS.Matter the run starts from. No member of the suite put it there.
- 02hands onSCRIBE → OPERATOR Profile, propose, check, render.A step following the one before it.
- 03parks hereOPERATOR NOT MECHANISED YET.Correction and its reason.Nothing later in this run reads it, so this is where that branch of the run stops.
- 04nothing crossesOPERATOR → SCRIBE Correction and its reason.This hand-off is not mechanised yet. A person notices, or nobody does.
- 05hands onMANIFOLD → SCRIBE hands on.A step following the one before it.
What this work delivers.
Structured records linked to their source documents, checked against a chosen schema and reviewed where interpretation is needed.
Choose the target
Define the fields and relationships the resulting records must carry. The target may be a hub, application or exchange schema.
Interpret the source
Scribe profiles the documents and proposes how their content maps to the target.
Render and review
Check the structured output against the source. Keep evidence links and flag ambiguous or unsupported values.
Capture corrections
An operator resolves exceptions. Corrections inform subsequent mappings without changing the original evidence.
Conforming a record does not prove its claim true. The source, its date and the quality of supporting evidence still matter.
Explore ScribeWhich tools, in what capacity.
Put this to work in your context.
Tell us what you need to achieve and what you already have.