The engine

Document quality starts before the model.

Sourcetrace is the document-structure engine under Sourceline. Where documents carry the decision, the system runs on Sourcetrace. It reads contracts, leases and project records as structure, not as flattened text, and preserves the layout, tables, annotations and page evidence before anything reaches a model. It is not sold on its own.

Read the standard

Local-first. Runs inside your environment or private Australian hosting.

What it preserves

Flatten the document and the structure is gone before the model runs.

A document is pulled in, turned into a run of text, chunked, embedded, and treated as if its structure did not carry meaning. Often the structure was the meaning. Sourcetrace keeps it.

  • Layout and reading order

    Columns, headers, footnotes and the order a person would actually read them, kept rather than collapsed into one stream of text.

  • Tables as tables

    Rows keep their relationship to columns. A figure stays attached to the period and the line item it belongs to, instead of becoming a loose number in a paragraph.

  • Annotations in context

    Comments, mark-ups and notes stay attached to the clause or cell they refer to, not detached into a separate list with no anchor.

  • Page evidence

    Every extracted element carries a reference back to the document and page it came from. That reference is what makes traceability possible downstream.

  • Confidence and diagnostics

    Where a read is uncertain, Sourcetrace exposes the uncertainty and the diagnostics behind it, rather than presenting an inferred result as a fact.

Why it matters

Traceability is built at ingestion, or not at all.

If the page reference is thrown away when the document is read, no amount of work later puts it back. The system can cite a source only if the source was preserved on the way in.

That is why Sourcetrace sits at the front of the pipeline. The five commitments in the standard, traceable above all, depend on what the engine kept.

Sourcetrace runs local-first, inside your environment or private Australian hosting. Your documents are not sent to a third-party service to be read.

  • In

    Contracts, leases, correspondence, project records, PDF and RTF bundles.

  • Through

    Structure preserved: layout, tables, annotations, page evidence, diagnostics.

  • Out

    A traceable document the system can reason over and still cite by page.

Engineering provenance

The lineage is in the open.

The structure-preserving approach behind Sourcetrace started as rtfstruct, an open-source parser that reads Rich Text Format as a structured document tree rather than as plain text. It is public, so the engineering thinking is open to inspection.

rtfstruct is published under Apache-2.0. See the source at github.com/keny369/rtfstruct, and the background in why we built rtfstruct.

How we engage
1

The Board Session

AUD 5,000, all in.

Your board sends its questions ahead. Every one comes back answered in writing. Then ninety minutes in the room, and you leave with decisions, not a presentation.

One week, end to end.

Book the Board Session
2

The Proof

AUD 9,500, fixed.

Pick the one job you think AI could do. A contract read. A report produced. A cycle shortened. We run it on your own material for two weeks. It works, or you get a written account of why it does not.

Start a Proof
3

The Build

From AUD 35,000, quoted after a Proof.

We build the system, fit the controls, and run it. One proposal, one number, and the running of it is in the number.

Talk about a Build