Hardline is an engineering system for documenting exposed utilities before walls close.
This public artifact shows the product thinking, system boundaries, and documented work of
co-founders Keenan Francisco and Caleb Ponce without publishing the production codebase.
Evidence boundary: the visualization uses a code-rendered scene and synthetic
utility data. It is not a field-accuracy result, customer scan, or performance claim.
SYN-042 / OPEN FRAMING / NORTH WALL
SYNTHETIC RECORD
REFERENCE FRAME / NORMALIZED
Interactive product-language sample. All detections and coordinates are synthetic.
One field workflow across three engineering surfaces.
The production system connects an iPhone capture client, an asynchronous processing
backend, and a browser review console. This diagram deliberately stops at architectural
boundaries; implementation and infrastructure remain private.
01
Capture
Phone-guided recording with spatial context and field feedback.
Swift / ARKit
02
Process
Queued reconstruction, detection, provenance, and record assembly.
Python / FastAPI
03
Review
Permissioned 2D and 3D inspection, correction, export, and sharing.
TypeScript / React
04
Return
Alignment-aware guidance back to the documented physical wall.
Swift / spatial math
Engineering decisions
The hard work was deciding what the system is allowed to claim.
The production history records a shift from feature breadth toward honest geometry,
observable failure modes, and a review trail that distinguishes measurement from inference.
Selected authored work / Keenan
Keep measurement and inference separate.
Coordinate provenance travels with the result. Measured wall-local positions,
approximate image-relative locations, and unreferenced detections cannot silently
collapse into one confidence claim.
position_basis
measured → wall-local frame
approximate → image-relative only
unreferenced → no position claim
Selected authored work / Caleb
Make the record usable beyond the scan.
The workflow became a full product surface: durable room identity, guarded uploads,
workspace access, 2D review, controlled sharing, quotas, and field-facing iOS feedback.
Treat a plausible picture as the beginning of validation, not the end.
Synthetic tests verify software behavior. They are not field evidence. Hardline's
validation contract requires physical ground truth before any measured accuracy claim.
Synthetic replay software checkMeasured pilot field observationReviewed report claim boundary
Contribution record
Built by Keenan Francisco and Caleb Ponce.
Counts below are attributed commits reported by GitHub for the private production
repository on September 8, 2026. Selected work was internally verified against authored
commit evidence; outside reviewers cannot inspect those private objects, and attribution
does not imply sole ownership of shared product decisions.