Start in about ten minutes
- Download the package.
- Generate AODM from what you already have — a web page, Schema.org JSON-LD, a CSV or an XBRL filing — or tag content by hand.
- Check it in the browser validator before you publish.
Or have us implement it
The specification is free and stays free. Your time is not. Ten minutes covers a page — a catalogue, an archive, a documentation set or a filing pipeline is a project, and we will take that on as one.
- Your content mapped, not rewritten. Entities, facts, relationships and rules derived from what you already publish, in the structure it already has.
- Markup on the pages that display it. Using the HTML embedding profile, so the human-readable and machine-readable versions cannot drift apart later.
- Provenance wired to real sources. Confidence, validity windows and derivation tracking set against where your claims actually come from — the part that separates AODM from ordinary structured data, and the part most easily got wrong.
- Validated, and left maintainable. Everything passes the conformance suite, and your team gets the conventions written down so the next hundred pages match the first.
- Long-term support, if you want it. Best value when your data moves — prices, availability, measurements, anything restated often. On a retainer we keep the markup current as the content changes, so every claim carries a confidence and a validity window that are true on the day someone reads it. When the specification itself moves, migrating your markup to the new version is included at no extra charge for as long as you are on support. Available from the start or added later.
Give us the address and we read the site: the price follows the amount of content on it and the types of content it turns out to be. Nothing is changed and nothing is stored but the measurements. Prefer to ask a person? Support@FucaSpark.com. Implementation and support are the only things here that cost anything: the specification, the schemas, the reference parsers and the validator are Apache 2.0, and that does not change.
Why FucaSpark
FUCA is the first universal common ancestor — the earliest thing in the line every living system descends from. It was not impressive. It was tiny, and researchers still argue over whether it was even a cell or something short of one.
What it had was a way to carry information forward accurately enough that everything complex could be built on top of it. AODM is small. What it makes possible is not.
AODM is a small set of tags. It is not the intelligence — it is the translation layer underneath it, the part that lets a claim carry its source, its confidence and its expiry date from one system into the next without losing them. Living data, and what sparks from it.
And it lets data imply. Rules over facts that carry their own source, confidence and validity window connect into new meaning, and record what produced it — instead of retrieving passages and guessing at how much each one should count.
What changes once it is running
AI cites you
A claim an engine can attribute and date is one it can repeat in its own answer, with your name on it, rather than working around you for a source it can verify.
Data arrives usable, not just parsed
A consumer that receives a source, a confidence and a validity window can decide how much weight to give a claim.
Superseded figures stop circulating
Expired knowledge drops out of present-tense queries while staying on record, so “what did we believe last March, and on what basis?” is now answerable.
Unit confusion becomes impossible
A quantity arrives as a number, a unit and a tolerance rather than a string every consumer parses for itself, differently, and occasionally wrongly.
Systems decline instead of guessing
“Does not require coolant” and “no information about coolant” stay distinct. A processor must honour that distinction or reject the document.
A retracted source takes its consequences with it
Invalidating an input finds every conclusion that transitively rests on it, instead of leaving them scattered with nothing linking them back.
Automated deduplication occurs upstream
The same statement arriving from two pipelines is recognised as one, so deduplication is not re-invented at every entry point.
Nothing has to execute
A few hundred bytes per tag, read by XPath, DOM parsers, lxml or any JSON library. No runtime dependency, no effect on page speed.
Adoption can be incremental
The quality features are optional attributes, so a consumer that ignores them still parses correctly. Start with entities and facts; add provenance and validity as your pipeline learns to use them.