Design and tracking, in the shape of #230, #234 and #366. Nothing here starts a build. It records the contract and splits the work into six milestones.
What
behold already draws drift and ownership on the live graph, and the carve lens already draws an advisor's score as a colour on the node. Nothing today draws what an estate costs, or where it runs out of headroom. That number cannot come from behold itself, because behold owns the picture, not the truth. It has to come from a chant lexicon, since chant is the source of truth and behold is chant that speaks choudoufu.
The engine contract
The engine stays abstract, held to a stated shape and nothing more specific.
Input: a resource graph, entities with a kind, a provider, a region and a size, and the edges between them. This is what chant already holds for any project, and what a choudoufu estate's live reads already hold.
Output, per entity and per estate, at a stated traffic level: cost per hour, headroom (how far from saturation on CPU and latency), an error-rate expectation, a resilience verdict under a named failure such as one zone lost, and a right-size suggestion. Every number carries provenance, meaning which engine, which version, its stated tolerance, and whether the figure is modeled from list prices or validated against a bill.
The invariant
behold never calls an engine, never holds its key, and never writes anything on its account. It renders what chant graph --live --overlay and the lexicon's report hand it, the same way it already renders drift and the carve score.
The rules
A prediction is never presented as a bill. A missing or unreachable engine means no overlay and a refusal that names why, never a locally faked number. The live path predicts the account as it stands, drift included. The declared path predicts the file. The two are shown as a delta.
Milestones
Refs INTENTIUS/chant#2355.
Design and tracking, in the shape of #230, #234 and #366. Nothing here starts a build. It records the contract and splits the work into six milestones.
What
behold already draws drift and ownership on the live graph, and the carve lens already draws an advisor's score as a colour on the node. Nothing today draws what an estate costs, or where it runs out of headroom. That number cannot come from behold itself, because behold owns the picture, not the truth. It has to come from a chant lexicon, since chant is the source of truth and behold is chant that speaks choudoufu.
The engine contract
The engine stays abstract, held to a stated shape and nothing more specific.
Input: a resource graph, entities with a kind, a provider, a region and a size, and the edges between them. This is what chant already holds for any project, and what a choudoufu estate's live reads already hold.
Output, per entity and per estate, at a stated traffic level: cost per hour, headroom (how far from saturation on CPU and latency), an error-rate expectation, a resilience verdict under a named failure such as one zone lost, and a right-size suggestion. Every number carries provenance, meaning which engine, which version, its stated tolerance, and whether the figure is modeled from list prices or validated against a bill.
The invariant
behold never calls an engine, never holds its key, and never writes anything on its account. It renders what
chant graph --live --overlayand the lexicon's report hand it, the same way it already renders drift and the carve score.The rules
A prediction is never presented as a bill. A missing or unreachable engine means no overlay and a refusal that names why, never a locally faked number. The live path predicts the account as it stands, drift included. The declared path predicts the file. The two are shown as a delta.
Milestones
Refs INTENTIUS/chant#2355.