AggloWorks“I’ll check with my office.”
Nine days later, the same question is back on the agenda. Meanwhile, someone is building on an assumption.
Ask once. Get an answer, or an owner and date.
A NEW WAY TO BUILD TOGETHER
One question.
One question.
One answer.
All the proof.
Ask the project, not five different inboxes. Get an answer cited to the current revision, while every company keeps its data its own.
One project. A 30-minute conversation. A clear next step.
ILLUSTRATIVE TIMELAPSE
ArchitectDesign intent
EngineerTechnical evidence
ContractorSite knowledge
OwnerProject requirements
One answer. Every source attached.···
Ceiling clearance, Level 0362 mmREV D ↗
ANSWERS MOVE. RECORDS STAY.SLOW ORBIT · TIMELAPSE
Your infrastructure Deny-by-default disclosure No central store of your records
BUILT FOR YOUR SIDE OF THE TABLEOwner / developer Main contractor Trade / consultant Professional services
01 / THE COST OF NOT KNOWINGLess chasing.
Less chasing.
More building.
The problem isn’t that nobody knows.
It’s that everyone knows something different.
And finding out has become a full-time job.
“Which revision are you on?”
The architect has Rev D. The installer has Rev C. Both are certain. The expensive part is what happens next.
Every answer pinned to its exact revision.“Not another shared platform.”
Your project already has enough logins. And your commercial manager isn’t about to hand over the mailbox.
Keep your tools. Keep control of your data.ONE QUESTION. SIX CHECKS. NOTHING TAKEN ON FAITH.Follow the evidence
- 01Ask
One plain-language question.
- 02Screen
Can this be known yet?
- 03Route
Find the parties who know.
- 04Pin
Agree the revision set.
- 05Reconcile
Show agreement. Or the gap.
- 06Record
Keep the evidence, together.
02 / NOT “TRUST ME.” “HERE’S WHY.”An answer with
An answer with
the receipts attached.
Not a chatbot with a confident opinion.
A structured answer you can check, trace,
and take into the room.
TRY A PROJECT QUESTION
This is a synthetic Fact Pack. Real-shaped evidence, fictional project. Explore freely. No sign-up, no sales gate.
Even the answer knows when it’s out of date.
A new drawing revision retires the old answer and notifies everyone relying on it. Try it.
03 / YOUR DATA. YOUR RULES.Share an answer.
Share an answer.
Not your business.
Each company runs its own agent, on its own infrastructure. You choose what it can answer—and how much it can say. If you haven’t said yes, the answer is no.
Enforced at your node, not our discretion Revoke access, with a recorded reason See what you disclosed, to whom, and when
And your raw mailbox? It stays home. YOUR DISCLOSURE DIALTRY IT
What can they ask about your delivery?
PREDICATE
WHAT THE PROJECT GETS“Yes. The switchgear arrives before energisation, with 6 days to spare.”
Your purchase price, supplier terms, and full schedule stay private.
Synthetic policy · no data connected
Bring the email. The PDF. The spreadsheet.
Leave the migration project behind.
In the proposed pilot, start with manual exports. Capture, redact, and approve inside your own node. Only a vetted, signed extract becomes askable.
Email & chatDrawings & PDFsSchedules & calendars
Inside your boundaryCapture → classify → redact → sign
PRIVATEA vetted extractCitable. Versioned. Revocable.
A hundred small questions can still reveal a big secret. The design includes purpose-bound queries, rate limits, cohort thresholds, and disclosure accounting. These limit inference risk; they don’t make it disappear.
04 / HONEST ABOUT WHAT’S NEXT“Not yet” is useful.
“Not yet” is useful.
If it comes with a next step.
Some facts don’t exist yet. AggloWorks is designed to name the prerequisite, the person who owes it, and the date—not invent a confident answer.
A contract artefact, not a forecast. The dependency graph is agreed by every party at kickoff, versioned, and changed only by agreement. Dates above are fictional, not jurisdiction-specific guidance.
05 / THE RECORD DOESN’T TAKE SIDES
Facts, not faith.
A record nobody can quietly rewrite. Every question, answer, refusal, and silence is recorded. Each entry links to the last. Each party keeps a witnessed copy.
Append-onlyHash-chainedReplayable
Don’t take the animation’s word for it. Recompute a real SHA-256 chain in your browser. Then change one fact.
A THREE-ENTRY DEMONSTRATIONLOCAL / SYNTHETIC
- Question recordedCeiling clearance · Level 03
Calculating… - Answer: 62 mmRev D · derived from geometry
Calculating… - Receipt recordedReferences the preceding answer
Calculating…
Real cryptography. No wallet. No network request.
The software prepares.
People still decide.
WHAT IT IS
A cited record of who knew what, when.
A way to make the factual half of meetings shorter.
An answer with visible disagreements.
WHAT IT WILL NEVER BE
An arbitrator, inspector, or certifier.
A worker-surveillance system.
A replacement for human responsibility.
A Fact Pack is a record, not a legal determination. It does not allocate liability, transfer design responsibility, or replace the contract’s dispute process. It is not a contractual notice unless the contract’s notice requirements are met. Proposed governance terms require project-specific legal review.
Procore.AUTODESK FORMAORACLE AconexDaluxkahua
The CDE stays the CDE. Quarksum is the proposed cross-company asking layer—not a replacement.
Names illustrate the tools your project may already use. Live integrations and partnerships are not claimed.
06 / A PLACE FOR EVERY PARTYDifferent interests.
Different interests.
Common ground.
You don’t have to share commercial interests.
You do need to agree on which drawing
you’re both looking at.
YOUR NEXT MONDAY
“I’ll check and get back to you.”An answer in the room. Or an obligation with a name and date.
Minutes come from the record. The meeting stays for decisions.
START SMALL. PROVE IT ON SITE.One real project.
One real project.
Not a leap of faith.
We’re developing AggloWorks with a bounded pilot in mind. Agree what success looks like before anyone signs. Then measure what actually changes.
30 minutes. A scoped pilot, or a clear no.Prefer email? aggloworks@quarksum.com
06 /parties at the table
03 /questions worth settling
90 daysto test what really works
Set the ground rules.
Contract Schedule, stage graph, disclosure policies, and version-authority map. Agreed together.
Ask real questions.
Test revision truth, design clearance, and delivery predicates on the project you’re already building.
Measure. Challenge. Decide.
Review answer time, stale-revision incidents, chasing hours, and participant cost. Continue or exit.
What we deliberately try to break
Refuse an answer: is the reason visible? Publish a new revision: are old answers retired? Submit two different calculations: is the disagreement shown? Rewrite history: does verification fail? Ask too early: do we get prerequisites instead of a guess?
Exit criteria and response-time targets are agreed in writing before the pilot. These are tests of the proposed system, not claims of measured results.
Free participation is the proposed model for parties who only need to answer.Project-funded pilot. Fixed scope and fee, agreed up front.
Need someone to run it? The instrumentation pack includes the Schedule, stage graph, policies, authority map, and facilitation. Optional operator arrangements must state witness independence and contractual exit rights; neutrality is not a vendor promise.
Get the draft Schedule CONCEPT STAGE · INTERACTIVE PROTOTYPENo borrowed credibility.
No borrowed credibility.
Just a mechanism you can inspect.
This page demonstrates the proposed product using synthetic data. It is not a live project network. Deployment, connectors, open-client delivery, and multi-party witnessing are pilot requirements—not shipped claims.
07 / FAIR QUESTIONSA little scepticism
A little scepticism
is a good thing.
Especially when the subject is trust.
Does everyone have to adopt another platform?
No migration is proposed: the CDE stays in place, and the pilot starts with six parties and manual exports. A free, phone-friendly participant client is part of the proposed model; live embedded integrations are not available in this prototype.
Am I handing over my mailbox or commercial data?
No. Capture, redaction, and approval happen inside your own node; only approved extracts are askable. Prices, personal information, and unrelated correspondence remain protected, with disclosure levels enforced by the owning party.
What if the answer can’t be known yet?
The question is marked ANSWERABLE, PENDING, or PREMATURE. Pending questions name the prerequisite, owner, and due date; premature ones name the stage and a smaller question to ask now. The agreed dependency graph—not a model’s guess—controls readiness.
What do I gain if an answer isn’t instant?
An obligation that cannot disappear into an inbox. The question is tracked, owned, and dated, with the intended answer delivered when its prerequisites clear. Time-to-answer and meeting questions closed are explicit pilot measurements.
What happens when two parties disagree?
Both positions, their inputs, and the gap are shown—not averaged away. AggloWorks identifies the smallest question that could settle the factual difference. People still decide entitlement, responsibility, and who pays.
Can it answer from an old drawing?
The design pins every answer to a revision set. A superseding revision retires affected answers and alerts their consumers; unresolved version authority returns UNRESOLVED, never a confident guess.
Who controls the record—and who operates it?
The proposed ledger is append-only, hash-chained, and witnessed by multiple parties. Governance can be owner-run, independently operated, or fully distributed, with audit and exit rights written into the Schedule. An operator must not be the only witness.
Does it make legal decisions or monitor workers?
Neither. It records evidence without deciding liability, replacing notices, or transferring design responsibility. Worker-level surveillance is excluded, and aggregate reporting must respect cohort thresholds.
Who pays, and is the product live yet?
AggloWorks is currently a concept with an interactive prototype, not a production service. The proposed model is a project-funded subscription and fixed-fee instrumentation pack, with free participation for small parties. Answering, refusing, and escalating must not be metered; pilot pricing and exit criteria are agreed before signing.
More “here’s your answer.”
Bring the question your project keeps asking.
We’ll start there.
Prefer email? aggloworks@quarksum.com