slack-app-level-token

Why the status is not stable

• empirical.corroborated.minimumReferences: 0 < 3 — Corroborated route (#177 amendment, 2026-09-24): at least three verified, dated references, each corroborating the shape the contract freezes. One rule or one example is a single point of failure. (corroborated route)
• empirical.corroborated.minimumOwners: 0 < 3 — The references must come from at least three distinct owners (a scanner vendor, the provider, a third party, this project's research). Two rules from one vendor, or a provider's docs page and its SDK, are one voice. (corroborated route)
• empirical.corroborated.minimumClasses: 0 < 2 — At least two corroboration classes other than a summary class. Peer scanner rules copy one another (#215 found tool shapes 'possibly copied from one source'), so scanner rules alone never qualify: one reference must be provider-owned code, a provider example or an independent implementation. (corroborated route)
• empirical.minimumObservations: 0 < 5 — Observed route (#205): five safe provider-issued observations are the minimum empirical sample. Since the 2026-09-24 amendment of #177 this route is optional: meeting it strengthens a T2 family's evidence basis to empirically-observed, and the corroborated route qualifies without any observation. (observed route, optional)
• empirical.minimumSubjects: 0 < 2 — Observed route: observations must span at least two pseudonymous accounts or projects. (observed route, optional)
• empirical.minimumIssuanceDates: 0 < 2 — Observed route: observations must span at least two issuance dates. (observed route, optional)
• empirical.minimumCorroborationClasses: 0 < 2 — Observed route: two corroboration classes, summary classes excluded, must agree with the observed structure. (observed route, optional)
• empirical.uncertainty: missing — explicit uncertainty is required
• empirical.supportedContexts: none — supported-context limits are required
• empirical.mode: missing — choose shape or context-constrained qualification