Rename DEPS to DEAS and define evidence-applicability boundaries

[mj3b]

Decision

Rename the working Decision Evidence Portability Specification (DEPS) to Decision Evidence Applicability Specification (DEAS).

The prior title implied that governance evidence, controls, findings, or legal conclusions can move across regimes without loss of meaning or force. The revised specification makes a narrower claim: one defined evidence artifact can be evaluated against one identified governance requirement for relevance, bounded assurance use, local evidence conditions, insufficiency, and non-equivalence.

Added

• canonical working-specifications/decision-evidence-applicability-v0.2.md;
• seven bounded determination states;
• explicit fields for applicability, assurance proposition, local evidence, sufficiency boundary, and non-equivalence;
• adjacent-system boundaries against Microsoft Agent Governance Toolkit, ScopeBlind/Acta, and Credo AI;
• migration language preserving the old DEPS path as a deprecated pointer.

Changed

• README badge, status table, contribution statement, architecture, evidence claims, repository map, and limitations;
• research claim C10 from portability to applicability, with a separate unsupported portability claim C11;
• framework evidence mapping to distinguish relevance from sufficiency;
• related-work analysis to separate runtime enforcement, receipt verification, policy-pack governance, decision records, human-influence assessment, and evidence applicability;
• limitations and changelog.

System boundary

• Microsoft AGT enforces and audits runtime actions.
• ScopeBlind/Acta verifies signed-receipt integrity and cross-implementation receipt behavior.
• Credo AI provides policy packs, control and compliance mappings, governance workflows, evidence collection, and runtime governance.
• GDI records one consequential decision.
• HIT evaluates whether human authority retained practical force.
• DEAS qualifies what a defined evidence artifact may support under one specified requirement.

Non-claims

DEAS does not provide runtime enforcement, policy compilation, a universal control library, signed-receipt conformance, cryptographic verification, legal compliance, certification, admissibility, or evidence portability.

Migration

The old DEPS file remains as a deprecation and migration pointer so existing links do not silently break. New work must use DEAS v0.2.0.