FASTBID24

AEC AI Lab · Experiment

Construction Provenance

Palynth.

Every object has a history. Now construction can remember it.

Palynth is the blockchain we had to build. Nothing in construction could prove its own history — which revision changed the hardware, who approved the substitution, why the order stopped matching the design. So we took blockchain technology, stripped away everything speculative, and kept the part that matters: an append-only chain of cryptographically linked events. Not a coin, not a token — a memory that can't be quietly rewritten.

Below: one hospital opening, five revisions, one quiet procurement conflict — every step recorded, connected, and provable.

Project

Northstar Medical Center

Asset

Opening 2147A

Status

Verified history

17 historical events7 connected assets10 source documents8 downstream impacts1 unresolved conflictCryptographically verified

Construction time machine

Simulated project · real engine

Drag through the revisions. Every state below is reconstructed live from the event ledger — not five saved pictures.

REV 01 · 2025-03-11The record begins
HAS DOORIN WALL TYPEREFERENCESOpening 2147PERMANENT UUID · SURVIVES RENAMESDoor D2147Frame F-2Hardware Set H17Wall Type WT12Mortise Lock L9010PO-1847
Configuration at REV 01

Opening 2147

doorType
WD-3
size
3'-0" × 7'-0"
fireRatingMin
60
room
Pharmacy 1120
electrified
no
frame
Frame F-2
hardware
Hardware Set H17
Recorded at REV 01

  • ASSET CREATED

    Door D2147 · WD-3 · Frame F-2 · HW Set H17 · 60 min · WT12

  • ASSET CREATED

    HG-1 · L9010 · C-60 · GSK-3 · TH-1

  • PO CREATED

    Line 12: Mortise Lock L9010 × 14 — per HW Set 17 as approved at A601 Rev 02

Change blast radius

Computed by graph traversal — not typed in
Change detected

Hardware Set H17→H21

Architectural revision incorporating the access-control requirement answered in RFI-027.

1 change8 dependencies7 documents1 procurement conflict

If FastBid24 had not caught this

Simulated impact

Why did this happen?

Current issue: PO-1847 contains a lock the design no longer uses. The ledger walks backward through its own cause links — the lineage of the decision, each step tied to evidence.

  1. What is the current issue?2025-07-30

    PO-1847: reviewStatus changed current → conflict. PO-1847 was generated before Revision 04 and still references Mortise Lock L9010 from Hardware Set H17. The approved configuration is now Lock L9080B inside Hardware Set H21 — what is on order no longer matches the approved design.

  2. Why does that condition exist?2025-07-29

    Substitution approved: L9080 → L9080B. Substitution accepted on the Rev 03 submittal — identical prep and voltage.

  3. What produced that state?2025-07-18

    Substitution proposed: L9080 → L9080B (L9080 factory lead time 16 weeks; functional equal proposed). Specified lock unavailable inside the project schedule.

  4. What changed upstream?2025-07-10

    Submittal 08 71 00 approved — No exceptions taken. Architect approved the Rev 02 hardware submittal.

  5. Why was that change made?2025-07-08

    Submittal 08 71 00 submitted for review. Hardware submittal prepared against the Rev 04 configuration.

  6. And before that?2025-05-20

    Opening 2147A: hardware set changed H17 → H21. Architectural revision incorporating the access-control requirement answered in RFI-027.

  7. And before that?2025-05-06

    Opening 2147A: rfi responded — Card access is required at this opening; revisions to follow.. Architect confirmed the access-control requirement.

  8. And before that?2025-04-28

    Opening 2147A: rfi created — Is card access required at Pharmacy Opening 2147?. Pharmacy 1120 stores controlled substances; the documents were silent on access control.

Not “change detected” — the reconstruction of why the current condition exists.

Opening passport

The first construction product passport

The complete identity of the physical opening — configuration, status, history, evidence, dependencies, risks. The same passport structure will carry an air handler, an electrical panel, or a glazing unit unchanged.

Identity
Opening
Opening 2147A
Internal identity
a0000001-2147…
Door
Door D2147A
Frame
Frame F-2E
Hardware
Hardware Set H21
Fire rating
60 min
Access control
Card Reader AC-17
Electrical
Power required
Current revision
REV 05
Standing

  • Approved configuration

    H21 · Lock L9080B per Submittal Rev 03

    verified

  • Procurement

    PO-1847 references superseded lock L9010

    conflict

  • Installation

    No installation events recorded yet

    current

  • History integrity

    17/17 events verified

    verified
  1. #00 · REV 01ASSET CREATED
  2. #01 · REV 01ASSET CREATED
  3. #02 · REV 01PO CREATED
  4. #03 · REV 02RFI CREATED
  5. #04 · REV 02RFI RESPONDED
  6. #05 · REV 02ASSET CREATED
  7. #06 · REV 02HARDWARE SET CHANGEDH17 → H21
  8. #07 · REV 03ASSET RENAMED2147 → 2147A
  9. #08 · REV 03ACCESS CONTROL CHANGEDnone → AC-17
  10. #09 · REV 03ELECTRIFICATION CHANGEDfalse → true
  11. #10 · REV 03FRAME CHANGEDF-2 → F-2E
  12. #11 · REV 04SUBMITTAL CREATED
  13. #12 · REV 04SUBMITTAL APPROVED
  14. #13 · REV 04SUBSTITUTION PROPOSEDL9080 → L9080B
  15. #14 · REV 04SUBSTITUTION APPROVEDL9080 → L9080B
  16. #15 · REV 04SUBMITTAL APPROVED
  17. #16 · REV 05PROPERTY CHANGEDcurrent → conflict

Verify the history

Recomputed on every click — nothing cached

Every event hash chains over the one before it on Palynth, FastBid24's construction blockchain. Verification recomputes SHA-256 over the canonical form of all 17 events and all 10 source fingerprints, live.

Tamper demo edits a copy — the ledger itself is immutable
Palynth anchor · future experimentNot operational

event hashesMerkle treePalynth rootpublic blockchain anchor

The Merkle root above is computed today. Anchoring it to a public blockchain would let a third party confirm the Palynth record existed unmodified at a point in time — without FastBid24 in the trust path. The event model is already shaped for this; the anchor is deliberately not built.

The ledger underneath

How Palynth remembers.

Every event on this page — a hardware change, a rename, an approval, a substitution — is content-addressed with SHA-256 and chained to the event before it. Each project's chain rolls up into a single Merkle root. Change one historical value, anywhere, and the entire chain refuses it: the edited event stops matching its own fingerprint, and every event after it stops matching the chain. That is the whole trick — and it's enough to make a construction record trustworthy.

Assets keep permanent identities under their drawing numbers, relationships close but never delete, and corrections append as new events — history is added to, never rewritten. The same machinery that proves the record also connects it: one change traces cleanly through drawings, hardware, submittals and procurement because Palynth holds the thread.

Palynth is a blockchain in the literal sense — a chain of cryptographically linked blocks of construction events — with none of the baggage: no tokens, no wallets, nothing to trade. Blockchain as trust infrastructure, not as a product — the reason the timeline above can say “verified” and mean it. Try it yourself: verify the chain, then tamper with a copy.

Append-onlyHash-chainedMerkle-rootedAnchor-ready
Palynth — connected block lattice

Every block chained to the last

Why this is not a doors feature

The model knows nothing about doors.

Assets, aliases, temporal relationships, hash-chained events, staleness, blast radius — every mechanism on this page is trade-generic. Doors & Hardware went first because FastBid24 already reads those documents in production. The same passport carries any of these unchanged:

Doors & HardwareElectricalHVACPlumbingFire ProtectionGlazingStructural SteelFF&E

This is not document comparison. This is the project remembering itself — and being able to prove its memory intact. Back to the Lab bench →

Want your revisions to stop surprising you?

Send a package — the takeoff and the coordination review come back in 48 hours.

Analyze my projectBook a working session