Test one system reading against answers your team already holds.
The test returns lineage, a graded report and a signed document.
How we work
The assessment is paid work on one system, and we are open to a paid proof of concept on that basis. You would choose the system and the question you need answered, and before anything starts we would agree with you what source we need to see and when the work will end. Whatever comes of it, the reading is delivered as files that stay with you, and the decision on whether to go further is yours.
Lineage, a graded report and a signed document are drawn from the same reading.
What it runs on
One system, one question and the source required to answer it.
The part you choose
It might be one reporting flow, one retiring platform, or the part you trust least.
Read access to source, under your controls
Code, schemas, jobs and configuration, granted and revoked your way.
One named technical contact
Who knows where the code lives and can resolve access questions.
Specialists check the answers the reading produced.
How the reading works across your systems is set out on the Product page, and what it takes for your reading is agreed at the start, against your inventory.
How long it takes
The end date is written before the work starts, once the chosen system and its source are known.
One reporting flow is at the short end, and a platform of several languages is at the long one.
What you receive
Three of the eight source-linked documents one pass returns. The lineage sheet is the Lineage record, the report is the Finding register and the signed document is the Evidence record, each traceable to lines of source, with the boundary of the supplied source marked.
The lineage sheet
Element-level lineage, derived from the code, running from the source through every transformation to the reported figure. The seal marks how far the supplied source goes.
The report
Findings ranked by what each touches, each with its confidence grade and a trace to lines.
The signed document
What the reading established and what it left unread, each listed against the total.
The same three documents, drawn from the published synthetic specimen, are on this site in full at what a reading returns, with every line resolving into a file you can open.
Bring your own answers
Compare the source reading with answers your team already uses, and retain each disagreement.
A mismatch begins adjudication, which means confirming scope, source availability, versions and test conditions before deciding what it means.
How it ends
On the written date, decide whether to continue, narrow the scope or stop.
Re-run it
A new reading after source changes.
Keep reading
Another part, another written end date.
End it
You revoke the access you granted. The record already delivered stays with you.
Compare one source reading with answers your team already holds.
The comparison starts with a result your team can already explain, then checks its source trace.
One page comes back, naming the four lines below.
- What it reads
- The part you choose, drawn by you.
- Access
- Read access to source, under your controls.
- The end
- A date written before the work starts.
- The decision
- Re-run it, keep reading, or end it, and the choice is yours.
Cosmogenesis was built in Sydney by a small team, and it is in a paid proof of value with an Australian bank today. Who we are