Loading…
Mobile Command Center · K1 Cloud
Field evidence, sealed at the point of work.
A box in the site trailer that needs no internet. The crew captures, a superintendent validates, the record is sealed and cannot be rewritten. The owner approves on that evidence from anywhere, and when there is a link the two sides reconcile.
Field capture
photo · voice · delivery
GPS + time burned in
SHA-256 on the device
works with no internet
Verified evidence
a named superintendent
capturer ≠ validator
rules checked at capture
Sealed record
hash-linked to the last
names the box by serial
recomputed on every read
Owner approval
one tap, on the evidence
sealed off site
reconciled to the site
capture → validate → seal → authorize → reconcile
■The box in the trailer seals the site’s record — capture, validation, the vault — with no internet.
◆Off-site decisions ride K1 Cloud: the owner’s one tap, the architect’s certification, sealed there.
⇄When there is a link, the two sides reconcile. Nothing waits on it; nothing is merged.
▣Raw media stays on site if the customer says so. The hashes travel; the photos need not.
Seven roles, one login
Who steps into K1?
The seven roles a construction contract already has. Each one signs in once, with one password, on the box in the trailer or on the project’s cloud side — wherever they stand.
◉
Field Worker
Captures the work — photo, voice, delivery — hashed on the device before it touches a network.
On site · the box
✓
Superintendent
Validates what the crew captured. The capturer can never validate their own record.
On site · the box
▤
Project Manager
Sets the rules and the schedule of values, raises change orders on sealed evidence, runs the site.
On site · the box
◕
Executive
Reads verified value against claimed value across the portfolio. Nothing to learn.
On site · the box
⬥
Architect / Engineer
Certifies a change order on the evidence it cites. Sealed where it happens.
Off site · K1 Cloud
⛓
Owner’s Representative
Authorizes in one tap, on sealed evidence, from anywhere. Sealed, and reconciled to the site.
Off site · K1 Cloud
◈
Owner Principal
The same one tap, for the person whose money it is.
Off site · K1 Cloud
The Mobile Command Center
On site. No internet needed.
K1 runs on a box in the site trailer, on the site’s own Wi-Fi, with its own database. The crew’s phones join it. Nothing on site waits for a connection.
- The rules — geofence, working hours, a schedule line, the media required — are checked at the moment of capture.
- Every capture is hashed on the phone before it touches the network, and sealed by the box, by serial.
- Everyone signs in with the password they set on K1 Cloud, cached on the box, no link required.
- Nightly, and whenever there is a link, the box reconciles with the project’s cloud side.
FieldTrailerSite Wi-Fi · no internet
How it works
From claim to approval, eight steps.
One loop, run on every project. The first step happens once; the rest happen every day.
1
CLAIM
The box claims its project by serial and a one-time code, and pulls the team, the rules and the schedule.
2
CAPTURE
Photo, voice, delivery. GPS and time burned in. SHA-256 on the device.
3
GATE
Geofence, working hours, a schedule line, the media required — checked at the moment of capture.
4
VALIDATE
A named superintendent promotes a capture to evidence. Never the capturer.
5
SEAL
Hash-linked to the record before it, naming the box by serial. Recomputed on every read.
6
VAULT
Searchable by words and by hash. Exportable as a package that re-verifies with no K1 involved.
7
DECIDE
The architect certifies, the owner authorizes — off site, on K1 Cloud, sealed there.
8
RECONCILE
Nightly, and whenever there is a link: each side hands the other what it sealed. Verified on receipt.
SealVerifyTwo sealed logs · nothing merged
The record
Two sealed logs. One record.
The site seals what happens on site. The cloud side seals what is decided off site. Each holds the other’s log verbatim, verified link by link, and neither is ever merged into the other.
SHA-256 per captureComputed on the device that took it, before any network.
Every link recomputed on readThe vault never trusts a stored hash; it proves the seal again each time.
Two sealed logs, nothing mergedThe site keeps its own; the cloud side keeps its own; each holds the other’s verbatim, verified.
Re-verifies without K1The export package carries the chain and the link function. A laptop with no K1 account checks it.
How K1 differs
Built for the field, not the office.
Office-first tools record what somebody typed later. K1 records what happened, where it happened, when it happened, and who saw it — and refuses to let anyone rewrite that.
K1
Runs in the trailer with no internet
Evidence sealed at capture, recomputed on read
Validation by a named second person, enforced
The owner approves in one tap, on the evidence
One record on site and off, reconciled
Seven roles, one login, defined once
vs
Office-first tools
Needs a connection to record anything
Photos in a folder, dated by whoever renamed them
Whoever uploaded it said it was fine
An email chain, a PDF, a signature block
Copies that drift and get argued over
Accounts per tool, per office, per site
What you get
Evidence that holds.
Evidence Vault
Every capture, organized and protected.
Search by words or by hash. Open a record and see who captured it, who validated it, and the seal that ties it to the record before.
Capture receipt
Time, location and context, burned in.
The worker sees the hash on the screen before anything is sent. GPS, time, the schedule line, the rules it passed.
Tamper detection
The seal is recomputed on every read.
Alter one sealed record and the next verification names the broken link. The drill is on the product’s own Settings screen; try it.
SEAL BROKEN · LINK NAMEDChange order on sealed evidence
The money moves only against verified work.
A change order cites sealed captures or it cannot be raised. The architect certifies, the owner authorizes, and both acts are sealed.
Export package
Court-ready. Re-verifies offline.
The chain, the link function, the instructions. Anyone can recompute it on a laptop, with no K1 involved.
What runs today
Not a deck. A product.
Everything on this page is built and running on K1’s servers and on a test site. No customer names are shown here because the first pilots have not started; when they have, their results will appear here as they are, not as we would like them to be.
● K1 Cloud — provisioning, the directory, the project’s cloud side
● Mobile Command Center — capture, gate, validate, seal, vault, export, offline
● Reconciliation — nightly and on demand, verified on receipt
◐ Pilots — applications open
- An application becomes a provisioned project with its own database, its own address and its own cloud side, with no hands.
- The jobsite team, the rules and the schedule of values are defined once on K1 Cloud, and the box pulls them when it is claimed.
- The box claims its project by serial and a one-time code, then runs with the internet cut: capture, gate, validate, seal, vault, export.
- The owner’s approval is made off site, sealed there, and reaches the site at the next reconciliation.
- One directory: a person set up on K1 Cloud signs in on the box, with no internet, with the same password.
Papers
Read the thinking.
MANIFESTO
Field First. Built with the End in Mind.
Why the crew’s phone and the trailer come first, and what a record has to be to hold up.
TECHNICAL WHITE PAPER
The K1 Operating System
Capture, gate, seal, vault, authorize, reconcile — the loop and the guarantees behind it.
WHITE PAPER
Sovereign Edge OS for Construction
A box on every site, a cloud that reconciles: sovereignty without giving up the office.
Run K1 on one job. Change every job after.
Apply for a pilot. The project is provisioned the moment it is approved; the box ships with it.