Skip to content

Platform

A project is a 3D grid of voxels -- small spatial cells that stand in for rooms, zones, and takt areas. Every real decision on the project attaches to one or more voxels: what was decided, who decided it, what it costs, and what it depends on.

That grid is the shared source of truth. A model, a schedule, and a punch list all describe the same project from different angles -- Ectropy resolves them into one container instead of three systems that quietly disagree.

Decisions carry a real authority chain, not a flat approval checkbox. Field inspections close the loop, validating that what was decided actually got built.

Looking up through the bays of an empty steel-frame structure at night, one bay lit amber

The model resolves into place

Its elements resolve into the spatial cells they occupy.

A model version is content-addressed the moment it's captured, so its frozen state carries a real spatial address, not just a filename. That address is the join everything else on this page attaches to.

resolve to the cells they occupyModel versioncontent-addressedElementsclaims about placeThe placespatial cell
A model version resolves its elements into the cells they occupy.

Decisions attach to a place, not a form

A decision is never edited -- only superseded.

Every decision on the platform carries its primary cell: who could decide, who did, when, and what it moved in cost. It can't be edited after the fact, only superseded by another decision that cites it, so the record reflects what actually happened in the field. That citation trail is exactly what a document attaches to next.

primary cellsupersedes, never editsDecisionauthority · person · time · costThe placespatial cell
A decision carries its primary cell and can only be superseded, never edited.

Documents cite the decision, not the other way around

The document is evidence attached to the decision, not the decision itself.

An RFI, a change order, a submittal, a drawing revision, a BCF topic -- whatever carried a decision in the field -- is cited on that decision, and through it, on the place. That's the structural difference between a document trail and a real authority record. Cost is the next thing that attaches to the same place.

cited onDocumentsRFI · CO · submittal · drawing rev · BCFDecisionauthority · person · time · cost
Documents are cited on the decisions they carried, not treated as the record itself.

Payment follows verified quantity, not a percentage

Payment is built to follow verified installed quantity, not a percentage.

Cost attaches to the place through the bill of materials. Payment follows what's actually verified in place, rather than a percentage on a schedule of values -- a narrower, harder claim than most schedule-of-values billing makes, and the one the platform's spatial container exists to support.

Bill of materialscostPaymentverified installed quantityThe placespatial cell
Cost and payment both attach to the same place a decision does.

Material intelligence, not a spreadsheet lookup

A voxel doesn't just hold a label -- it knows what it contains. If a voxel is a GA-WP-3 one-hour-rated partition, the platform knows a 15mm deviation voids the rating. That's the difference between a system that stores a spec and one that can tell you when the spec has actually been violated. That same per-voxel intelligence is what the platform's current stage reflects next.

Where the platform is today

The decision and authority layer -- who can decide what, and the record it leaves -- is built and deployed. The spatial container that resolves a model, a decision, a document, and a payment onto the same place is in active development, in the order this page just walked through.

See it on a real project

See it on a real project.