DEST v0.8 — Fixed-Cost Certificate Cascade Model
Weighted-Coverage Theorem, Exact Small-DAG Census, and Minimal Mixed-Utility Counterexamples
Version: v0.1
Date: 2026-08-14
Engineering parent: DEST Runtime v0.7-alpha
Status: theorem-style mathematical submodel + executable exhaustive checks
Abstract
DEST Runtime v0.7-alpha empirically separated three regimes:
- pure certificate-cascade structure;
- belief-conditioned evidence transfer;
- deadline/dynamic-cost scheduling.
On its frozen holdout, sampled diminishing-return violations were:
[ 0/30000 ]
for the pure structural cascade,
[ 1963/30000 ]
after belief transfer, and
[ 20309/30000 ]
after deadline/dynamic-cost effects.
This paper asks whether the first zero-violation result reflects a genuine theorem.
The answer is yes, but only after separating two different utilities that v0.7 had combined.
Pure Cascade Coverage
Let every inspection (i) have a fixed deterministic affected set , and let every affected certificate/debt target (v) have a fixed nonnegative weight . Define:
Then is a weighted coverage function and therefore is:
For certificate DAGs, may be the descendant closure of certificate (i). The proof does not actually require acyclicity; it requires only that each action's affected set be fixed independently of the selected set and history.
Mixed Revoke–Release Utility
The v0.7 structural runtime additionally gave value to confirming a valid quarantined node, but removed that release value when an invalid ancestor revoked it.
That creates terms of the form:
where is the set of invalid inspections whose cascade blocks the release of valid node (u).
This term is not universally submodular when:
A three-node counterexample exists.
Therefore:
but:
The paper proves a useful sufficient condition:
implies that the mixed utility remains submodular, though it need not be monotone.
An exact exhaustive program accompanies this paper. It enumerates every ordered DAG up to , representing every finite DAG structure up to a topological relabeling, and checks the pure coverage diminishing-return inclusion property. It also searches all valid/invalid status assignments for minimal mixed-utility counterexamples.
1. Why v0.8 exists
The goal is not to claim that the complete DEST Runtime is submodular.
v0.7 already falsified that.
Instead, v0.8 asks:
Which exact substructure generated the zero-violation empirical signal?
This is an inversion of the usual workflow:
Runtime experiment
→ structural regularity
→ mathematical isolation
→ theorem
→ exact census
→ minimal counterexample to overgeneralization
2. Fixed Cascade Model
Let:
be a finite inspection/action set and:
be a finite target universe.
Each inspection has a fixed affected set:
Each target has weight:
For selected inspections , define:
Then:
For a certificate DAG , one canonical choice is:
and:
the node together with every deterministic downstream certificate invalidated by the cascade.
3. Theorem 1 — Normalization
Proof
Therefore the weighted sum over the covered set is zero.
4. Theorem 2 — Monotonicity
If:
then:
Proof
Because union is monotone:
All are nonnegative, so adding covered targets cannot decrease total weight.
5. Theorem 3 — Submodularity
For:
define marginal gain:
Then:
Proof
The newly covered targets after adding (e) to (S) are:
Similarly:
Since:
we have:
Hence:
Therefore:
Thus is submodular.
6. Corollary — The DAG is not the source of submodularity
The proof uses only:
and:
Therefore acyclicity is not necessary for the set-function theorem.
The DAG remains important to DEST because:
- it encodes certificate semantics;
- it gives a natural downstream closure;
- it supports revocation provenance and replay.
But the mathematical source of submodularity is:
7. Fixed Costs
Assign every inspection a fixed cost:
A budget constraint is:
This changes the feasible family of sets, not the utility:
Therefore:
They change the optimization problem from cardinality-constrained selection to a knapsack-type constraint.
For equal costs / cardinality (k), the classical monotone-submodular greedy result of Nemhauser, Wolsey, and Fisher applies to this model. This paper does not claim the same bound for naive cost-ratio greedy under arbitrary costs.
8. Why v0.7's full structural utility is different
v0.7 also modeled valid quarantined claims.
Let:
- : inspections with deterministic invalid outcomes;
- : inspections with deterministic valid outcomes.
Invalid inspection revokes a fixed closure .
For each valid node , define blocker set:
A valid inspection (u) receives release value only if no selected invalid blocker revokes it:
The mixed utility is:
The first term is weighted coverage and is submodular.
The second term is where the theorem can break.
9. Proposition 4 — Monotonicity is not guaranteed
Consider two inspections:
where (a) is invalid and (u) is valid.
Let:
Then:
while:
Thus:
Therefore mixed revoke–release utility need not be monotone.
10. Lemma 5 — A release term with zero blockers is modular
If:
then:
This is modular, hence submodular.
11. Lemma 6 — A release term with one blocker is submodular
Suppose:
Then:
The only nonzero positive marginal is adding (u) before blocker (a) is selected.
Adding (a) has marginal:
when (u) is present and zero otherwise.
For every:
the marginal at (T) never exceeds the marginal at (S).
Hence is submodular.
12. Theorem 7 — Blocker-At-Most-One Sufficient Condition
If:
then:
Proof
The revocation term is a weighted coverage function, hence submodular.
By Lemmas 5 and 6, every release term is submodular.
A finite sum of submodular functions is submodular.
Therefore is submodular.
This theorem does not imply monotonicity.
13. Proposition 8 — Two blockers destroy the universal guarantee
Suppose a valid node (u) has two distinct blockers:
and:
Consider only the release term .
Set:
Then:
because adding (a) removes the release of (u).
But (u) is already blocked in (T), so:
Submodularity would require:
which is false.
Thus is not submodular.
Therefore if any positive-release valid node has two blockers, no universal submodularity guarantee exists for all nonnegative revocation weights: choose those revocation weights to be zero, or sufficiently small, and the violation survives.
14. Universal Characterization for the Mixed Model
For the model class in which revocation coverage weights may be arbitrary nonnegative values:
if and only if:
The forward direction is Theorem 7.
The reverse universal statement follows from Proposition 8.
15. Minimal counterexamples
15.1 Non-monotonicity
Minimum ground-set size:
Structure:
a (invalid)
|
v
u (valid release)
Selecting (u) first produces release value.
Adding (a) removes it.
15.2 Non-submodularity
Minimum ground-set size:
Structure:
a (invalid) ─┐
├─> u (valid release)
b (invalid) ─┘
With:
the marginal of (a) rises from negative to zero after more information/actions have already blocked (u).
That is increasing returns, not diminishing returns.
16. Exact Small-DAG Census
The accompanying program performs two exact censuses:
- pure coverage: every forward-edge DAG on ;
- mixed valid/invalid assignment regression: every forward-edge DAG and assignment on satisfying the tested scope.
The smaller mixed cutoff is an execution bound, not a theorem bound.
For fixed topological labels, the number of DAG edge sets is:
Every finite DAG admits a topological ordering, so every DAG structure can be relabeled into this forward-edge representation.
For pure coverage, the program checks the stronger set inclusion:
for every:
This implies diminishing returns for every nonnegative weight vector, not merely one sampled weight assignment.
The program separately:
- finds the minimum non-monotone mixed model;
- finds the minimum non-submodular mixed model;
- exhaustively checks all status assignments through satisfying with deterministic positive regression weights.
The theorem for arbitrary nonnegative weights is analytic; the mixed census is a regression companion rather than its proof.
16.1 Exact census result
The completed executable census reports:
Pure cascade coverage
- ordered DAGs through : 1099;
- exact new-coverage inclusion checks: 421861;
- violations: 0.
Full mixed model at
Using fixed positive regression weights
the census contains 1098 complete DAG/status models.
Among them:
- 537 are non-monotone;
- 160 are non-submodular;
- exactly 160 contain at least one positive-release valid node with two or more invalid blockers;
- all 160/160 of those models are non-submodular under this fixed regression weight assignment.
Blocker-at-most-one regression region
The census contains 938 models satisfying for every valid release node. Observed submodularity violations: 0/938.
This computational result is consistent with Theorem 7. The proof, not the census, carries the arbitrary-weight claim.
Minimal exact witnesses
The first non-monotone model has two nodes:
0 invalid -> 1 valid
with and .
The first non-submodular model has three nodes:
0 invalid -> 1 invalid -> 2 valid
where valid node 2 has blockers . The exact witness is
with
Thus even a single chain, rather than a branching fork, is enough to destroy the universal mixed-utility guarantee.
17. Belief Transfer
Once inspection results update another debt's estimated probability:
the objective becomes history-conditioned.
It is no longer represented by one fixed set function:
Classical submodularity is therefore no longer automatically the right object.
One may ask whether an adaptive-submodular model exists, but only after specifying:
- outcome space;
- partial realizations;
- conditional expected marginal values;
- prior;
- observation model.
v0.7 empirically observed nonzero diminishing-return violations after belief transfer.
Therefore DEST currently has no general adaptive-submodularity theorem.
18. Deadlines and Dynamic Costs
If the score of inspection (i) depends on clock time:
then the same selected set can have different value depending on ordering and time.
Likewise:
changes the feasible continuation as time evolves.
Thus the full runtime is not one static set-function maximization problem unless time is explicitly encoded into the state/ground elements.
v0.7's high violation rate in the deadline/dynamic-cost diagnostic is therefore not surprising: the fixed-set diminishing-return law is being tested outside its natural static scope.
19. What v0.8 proves
20. What v0.8 does not prove
It does not prove:
- full DEST is submodular;
- full DEST is adaptive submodular;
- v0.7 scheduler has a greedy approximation guarantee;
- deadline urgency preserves submodularity;
- probability calibration preserves adaptive diminishing returns;
- dynamic costs preserve an approximation factor;
- branch interactions can always be reduced to coverage;
- quarantine release is harmless to monotonicity.
21. External alignment
Coverage functions are a standard special case of submodular functions.
The classical Nemhauser–Wolsey–Fisher analysis studies greedy maximization of nondecreasing submodular set functions under a cardinality constraint and obtains the familiar limiting (1-1/e) guarantee.
Adaptive submodularity generalizes diminishing returns to partial observations, but its guarantees require its structural assumptions to hold.
DEST v0.8 uses these theories only where their hypotheses match the isolated submodel.
22. Engineering consequence
The Runtime should stop asking:
Is DEST submodular?
The correct question is:
Which utility components are submodular, which are not, and which runtime transitions move us between those classes?
This suggests a future scheduler can route by certified structural regime:
PURE_CASCADE_COVERAGE
→ monotone submodular backend allowed
MIXED_RELEASE, blocker_count <= 1
→ submodular but possibly non-monotone backend
MIXED_RELEASE, blocker_count >= 2
→ no universal submodularity guarantee
BELIEF_UPDATE
→ adaptive diagnostic required
DEADLINE / DYNAMIC_COST
→ state/time-dependent optimization backend
23. Final conclusion
The empirical zero-violation signal from v0.7 was real, but its correct interpretation was narrower than:
What survives mathematical isolation is:
And therefore:
The first principled break occurs not merely because "AI is dynamic", but already in a three-node deterministic mixed utility:
That gives DEST a sharper mathematical boundary:
This is the first point in the Runtime engineering line where an empirical regularity has been compressed into a theorem and then deliberately surrounded by exact counterexamples.