Policy Cards External Framework Crosswalk
Generated Evaluation Status
This section is generated from the framework manifest and compatibility report. Do not edit it manually.
- Framework ID:
policy-cards - Manifest:
docs/external-frameworks/policy-cards.json - Compatibility report:
./reports/policy-cards.compatibility.json - Evidence class:
SOURCE_REVIEWED - Independently reproducible:
False - Comparative-testing claim allowed:
False - Missing reproducibility gates:
shared_test_vector, raw_output, timestamp, runtime_configuration, source_version_or_hash, replay_commands, declared_expected_outcome, independent_reproduction - Evaluation result:
COMPATIBILITY_EVIDENCE_ONLY - Cycle status:
FIRST_FRAMEWORK_CYCLE_COMPLETE - Execution authority claim:
False - Next bounded action: Add executable observations, raw outputs, pinned versions, replay commands, and independent reproduction before making comparative-testing claims.
- Posting source: generated compatibility report
- Generated status is descriptive compatibility evidence only.
Generated Authored Analysis Boundary
This section is generated. Do not edit it manually.
- Framework ID:
policy-cards - Framework name:
Policy Cards - Generated sections above this boundary may be rebuilt from registry, manifest, compatibility-report, and result artifacts.
- Authored analysis below this boundary may contain interpretation, notes, and framework-specific discussion.
- Generators must preserve authored analysis unless a future validator explicitly declares a migration path.
- Boundary rule: generated material is descriptive compatibility evidence only and does not create certification, endorsement, adoption, proof, or operational permission.
Generated Transition Mapping
This section is generated from the framework manifest. Do not edit it manually.
| Field | Generated Value |
|---|---|
framework_identity | Policy Cards |
source_reference | https://arxiv.org/abs/2510.24383 |
source_version | public source recorded |
allowed_use_boundary | machine-readable policy artifact crosswalk evidence only |
claims | deployment-layer policy artifact, operational constraints, regulatory constraints, ethical constraints, allow/deny rules, evidentiary requirements |
non_claims | no admissibility proof, certification, endorsement, or execution authority |
input_artifact_type | machine-readable policy card artifact |
output_artifact_type | crosswalk and compatibility evidence |
actor_or_authority_model | external policy-artifact posture; no StegVerse authority inherited |
evidence_model | evidentiary requirements and policy metadata |
policy_or_rule_model | allow/deny rules and obligations |
delegation_model | not asserted by wiki entry |
decision_or_result_model | runtime policy evidence only |
execution_authority_claim | false |
receipt_or_trace_model | source reference and wiki record |
reconstruction_model | source plus crosswalk can reconstruct policy-artifact relationship limits |
SPE_overlap | may inform policy reference and evidence posture, not standing determination |
StegVerse_ecosystem_overlap | Transition Table, Runtime Transition Governance, Policy Reference, Evidence Posture |
fail_closed_conditions | missing source, undefined mapping, policy overclaim, or authority overclaim |
Generated mapping is compatibility evidence only.
Generated Framework Metadata
This section is generated from the external-framework registry. Do not edit it manually.
- Framework ID:
policy-cards - Name:
Policy Cards - Registry status:
SOURCED-CROSSWALK-PROVISIONAL - Testbench state:
SOURCE_RECORDED_CROSSWALK_PROVISIONAL - Manifest path:
docs/external-frameworks/policy-cards.json - Source reference:
https://arxiv.org/abs/2510.24383 - Metadata boundary: generated metadata is descriptive only; it does not create certification, endorsement, formalism adoption, admissibility proof, or execution authority.
Status
Relationship type: external framework crosswalk
Canonical StegVerse formalism source: Admissible-Existence
External framework role: machine-readable runtime governance artifact
Wiki role: convergence, mapping, and relationship review
Citation status: sourced
Evidence provenance status: Batch 4 refactor installed
Source
Public source: https://arxiv.org/abs/2510.24383
Evidence Provenance
| Evidence Class | Current Evidence | Status | Missing Fields |
|---|---|---|---|
| Official Framework Sources | Public arXiv source URL. | present | Versioned source snapshot and source hash. |
| Official Implementation Sources | Treated as paper/artifact-dependent; no implementation package is attached on this page. | paper_or_artifact_dependent | Policy-card schema, examples, release, repository, or commit reference if available. |
| Observed Behavior | No runtime behavior is claimed. | not_started | Policy-card input artifact, output, timestamp, and source version. |
| Reproduced Behavior | No independent reproduction is claimed. | not_started | Reproduction fixture for parsing/evaluating a policy-card artifact. |
| StegVerse Analysis | Deployment-layer artifacts, constraints, allow/deny rules, and evidentiary requirements are mapped to admissibility primitives. | runtime_policy_artifact_crosswalk_with_page_provenance | Concrete Policy Card-to-Commitment-Candidate fixture. |
| Interoperability Assessment | Policy Cards may supply policy/evidence material for StegVerse review, not authority. | pending_policy_artifact_fixture | Fixture and compatibility report. |
| Standing | Sourced provisional. | provisional | Source snapshot and fixture. |
Evidence classification:
F1: public Policy Cards source URL and paper-native claims.
F2: pending until implementation/schema/artifact package is attached.
S1: StegVerse interpretation of Policy Cards as runtime policy/evidence artifacts.
S2: mapping to Transition Table, Runtime Transition Governance, Policy Reference, Governance Boundary, Evidence Posture, Receipt-Bound Execution, and Core-Lite Admissibility Engine.
H1: future policy-card fixture until concrete artifacts are attached.
Definition
Policy Cards are presented in their source paper as machine-readable deployment-layer artifacts for expressing operational, regulatory, and ethical constraints for AI agents.
Framework-Term Definitions
| Native Policy Cards Term | Definition For This Wiki | Reconciliation Class | Admissibility Relationship |
|---|---|---|---|
| Policy Cards | External machine-readable deployment-layer policy artifacts. | new | Preserved as framework-native artifact terminology. |
| Deployment-layer artifact | A governance artifact intended to operate near deployment/runtime use. | adjacent | Related to Core-Lite Admissibility Engine. |
| Operational constraints | Machine-readable constraints on agent operation. | adjacent | Related to Policy Reference and Governance Boundary. |
| Regulatory constraints | Machine-readable constraints derived from regulatory duties. | adjacent | Related to Policy Reference. |
| Ethical constraints | Machine-readable constraints derived from ethical requirements or posture. | adjacent | Related to Review Posture and Governance Boundary. |
| Allow/deny rules | Machine-readable rules that permit or deny actions under conditions. | adjacent | Related to Transition Table and Runtime Transition Governance. |
| Evidentiary requirements | Requirements for evidence that must exist or be supplied. | adjacent | Related to Evidence Posture and Receipt-Bound Execution. |
Relationship To Admissibility
Policy Cards are useful as a runtime-governance and policy-artifact crosswalk target.
They do not replace commit-time admissibility review, execution authority checks, receipt-bound execution, or Admissible-Existence formalism sources.
Crosswalk Targets
| Policy Cards Function | Wiki / AE Relationship |
|---|---|
| Allow/deny rules | Transition Table; Runtime Transition Governance |
| Obligations | Policy Reference; Governance Boundary |
| Evidentiary requirements | Evidence Posture; Receipt-Bound Execution |
| Runtime enforcement mapping | Core-Lite Admissibility Engine |
Non-Claims
Policy Cards are not a StegVerse canonical formalism.
Policy Cards do not prove transition admissibility.
Machine-readable policy artifacts do not automatically grant execution authority inside StegVerse.
Challenge Path
A reader may challenge this reflection by identifying the claim, challenged field, reason, supporting evidence, and requested correction or standing change.
Mandatory Footer
This page reflects a bounded admissibility packet. Publication does not create standing. The reflected claim inherits only the standing that can be reconstructed from the referenced evidence, authority, and admissibility conditions.