Planned capabilities
Specified and not implemented. Named so the omission is visible.
declared status: planned 10 claims declared
-
A task will know which commits it produced, rather than inferring them from a range
—
recorded evidencerecorded evidence: no test
-
Opt-in runtime adapters will clamp read size, output size and fan-out from profile-derived limits
—
recorded evidencerecorded evidence: no test
-
Execution telemetry will be recorded once a provider exposes it honestly
—
recorded evidencerecorded evidence: no test
-
Majordomus will state a total-token change only from matched, verified runs that meet the methodology's publication rule
—
recorded evidencerecorded evidence: no test
-
Cost per accepted outcome will be reported from measured data only
—
recorded evidencerecorded evidence: no test
-
Routing recommendations will be derived from measured cost and outcome data
—
recorded evidencerecorded evidence: no test
-
One policy will be shared across repositories and workers
—
recorded evidencerecorded evidence: no test
-
A milestone will be closed on GitHub only once the intents it realises are satisfied
—
recorded evidencerecorded evidence: no test
-
A criterion settled by a command or by a deployment will be met by recorded evidence
—
recorded evidencerecorded evidence: no test
-
No pull request can be merged into the default branch while the verdict status is red, because a branch rule requires it
—
recorded evidencerecorded evidence: no test