Method

Definition

aSFD = nominal deck area × days the hull is AVAILABLE. Available is a three-part test, all three required: waterborne (not hauled, not on the hard), rated (no open defect suspending the load placard), reachable (moored inside a service area a customer can use). Today only the first part is implemented; available means not hauled, and the figure says so in its note.

Available, not leased, because a cost denominator must not move with sales performance, because availability is the physical fact a node can attest while a lease is a contract fact, and because every capacity analogy Thalor reaches for (nameplate watts, payload kilograms, provisioned instance-hours) uses capacity with utilisation as a separate multiplier.

Counting rules

• D-2 A hauled asset earns zero aSFD even while the lease runs.
• D-3 Whole UTC days. A day is logged only when a verified session covers at least 20 h of it at capture ≥ 99% and the session is waterborne.
• D-4 Nominal square feet = length × beam, set once per asset class, forever. Ode-20 = 200 sq ft.
• D-5 Deployed-unpaid ground (demos, trials) is available ground and counts toward aSFD; it is excluded from leased aSFD and from revenue.
• One denominator Nominal SFD = nominal sq ft × calendar days, on both sides of every ratio. Haul-out enters in exactly one place, availability (= aSFD ÷ nominal). Planned haul days are a memo and appear in no denominator.
• Revenue A prepaid fixed-term contract accrues at contract value ÷ term days, never at an annualised rate card.

The Goodhart guard

aSFD rises when you build steel. Occupancy (leased ÷ available) is emitted in the same object and is never shown without it, on any page, endpoint or export. Revisit trigger: if occupancy sustains below 50%, available becomes a vanity number and the definition is re-argued.

Evidence classes

MEASURED an instrument produced it, source and date stated · REPORTED an authority or party filed it · DERIVED computed from MEASURED or REPORTED inputs · FORECAST not yet measured. A figure with no class is an error, not a fact. Watch never promotes a class; only a node emitting a field, or a counterparty signing, promotes it.

What is attested today, and what is not

• Logged aSFD is MEASURED: each logged day is backed by a session bundle whose every file re-verifies against its own checksums, whose capture is computed on monotonic time, and which is waterborne.
• Waterborne is REPORTED, not measured: session type is not BENCH and the GNSS stream carries at least one fix. Motion and position inference are not yet in the path.
• Capture, waterborne and the clock correction are derived by Watch at ingest and labelled so on every session (derived_by_watch). The interface ask to OSea (WATCH-IFC-1) is that the node emit them.
• Worked SFD stays FORECAST until an operator log or node utilisation supplies it. The 0.7 Worked/Leased ratio is never reported as measured.
• Annual opex is REPORTED from an unquoted placeholder and is the least-validated input in the company.
• Unforgeability is not claimed against an insider with physical access to a single node. Diverse custodians (nodes that refuse non-chaining snapshots, external anchors, counterparty witnesses) are what make history hard to rewrite; cross-attestation between hulls arrives with the second hull.

Where humans stay

No human stands between evidence and number: export, transfer, verification, ingest, attestation, the ledger tick, the snapshot, the anchors and the site build are all a process. Humans remain where the facts are contracts, not sensors: registering a lease, a haul-out or a launch date is a signed commit to the registry, which the Log then reads. An unresolved primary record pauses the Log and the site says so.

Privacy

No home coordinates, no credentials, no personal data on the public tier. Position is published at harbor resolution or not at all. The public build is scanned for forbidden patterns before it is swapped in; a build that fails the scan is not published.

THA-MET-001 Rev 1 (amends Rev 0, D-1…D-5) · THA-MET-002 Rev 0 · THA-STD-001 §0.2 · THA-WATCH-001 Rev 0.1 (NAME-2)