AARP Claims Dictionary

The machine-readable vocabulary behind AARP verified claims, limitations, reserved axes, and overclaim-risk warnings.

Ready to protect your own setup?

An AARP appraisal reports a claim set, not a trust score. Each claim name says what the verifier mechanically confirmed, and the paired limitations say what a reader must not infer from that evidence.

This page renders from the public JSON dictionary shipped with the Pipelock SDK. The human page is a view of that source, not a separate hand-maintained table.

Reserved entries are vocabulary locks. They name future transparency, deployment, and authority claims, but the current verifier does not emit those claims until the evidence and hostile fixtures exist.

Profile: aarp/v0.1

Source: aarp-claims-dictionary/v0.1. Reserved entries freeze names only; the current verifier does not emit reserved claims.

Emitted Verified Claims

ClaimAxisStatusProvesDoes not proveTested by
receipt_signature_validintegrityemittedAt least one parallel AARP signature verified under a trusted key over the canonical signed assertion payload.
  • transparency-log inclusion
  • policy correctness
  • action safety
  • complete mediation
g01-single-ed25519-mediated
mediator_key_pinnedidentityemittedA verifying signature's key id is bound by a verifier-side trust entry to the asserted mediator identity, role, and trust domain when scoped.
  • that the mediator made a correct decision
  • that all traffic was forced through the mediator
  • that the key was never compromised
g01-single-ed25519-mediated
receipt_timestamp_monotonic_chain_presentintegrityemittedThe signed assertion carries a well-formed Rung-1 chain link with a sequence number and prior payload hash.
  • that the whole stream was verified as contiguous
  • wall-clock freshness
  • absence of omitted actions
g03-chain-genesis-linked
signing_workload_svid_chain_validatedidentityemittedThe X.509-SVID leaf chain validated offline against the pinned bundle at action time and the SPIFFE ID was permitted.
  • that the workload's egress was non-bypassable
  • that deployment policy was enforced
  • that JWT-SVID evidence is equivalent
s01-valid-ecdsa-p256-baseline
signing_workload_svid_boundidentityemittedThe SVID leaf key signed the receipt and assertion binding, proving possession by the signing workload identity.
  • deployment attestation
  • network non-bypass
  • that local side effects were mediated
s01-valid-ecdsa-p256-baseline
signing_workload_svid_valid_at_action_timefreshnessemittedThe X.509-SVID was valid at the action time under the pinned historical bundle.
  • that the assertion was published promptly
  • that the key remained uncompromised later
  • that the chain was witnessed externally
s01-valid-ecdsa-p256-baseline

Reserved Verified Claims

ClaimAxisStatusProvesDoes not proveTested by
policy_hash_boundauthorityreservedReserved for the claim that the decision policy hash is bound into the signed assertion.
  • that the policy was correct
  • that the policy was enforced across unmediated traffic
  • that every evaluator used the same policy
reserved-policy-hash-bound
receipt_timestamp_contiguous_chain_verifiedauthorityreservedReserved for stream-level verification that an issuer chain is contiguous for the checked range.
  • external witnessing
  • complete action-stream submission
  • absence of records before or after the checked range
reserved-contiguous-chain-verification
external_witness_checkpoint_signature_validtransparencyreservedReserved for verification that an external witness signed the checkpoint being checked.
  • that all receipts were submitted to the witness
  • that the witness showed the same view to every verifier
  • that the checkpoint covers a specific action
reserved-external-witness-checkpoint-signature
receipt_chain_root_matches_witnessed_checkpointtransparencyreservedReserved for verification that the receipt-chain root matches the externally witnessed checkpoint root.
  • that omitted receipts do not exist
  • that the witness is globally consistent
  • that every action stream was submitted
reserved-chain-root-witness-match
witness_checkpoint_covers_chain_seq_rangetransparencyreservedReserved for verification that a witnessed checkpoint covers the asserted issuer chain sequence range.
  • that all receipts before the range were submitted
  • that actions outside the range were mediated
  • absence of split-view without gossip
reserved-witness-checkpoint-range
witness_checkpoint_observed_at_timetransparencyreservedReserved for verification that the external witness observation time for a checkpoint was recorded and validated.
  • wall-clock correctness beyond the witness evidence
  • that the receipt was emitted at that time
  • that no later omission occurred
reserved-witness-checkpoint-observed-time
witness_checkpoint_gap_bounded_observedtransparencyreservedReserved for observing that the witness-silence interval after the last witnessed checkpoint stayed within the configured bound, assuming process, clock, witness path, and deployment boundary were operating.
  • absence of omitted actions
  • that every receipt was submitted to the witness
  • that the deployment boundary was non-bypassable
reserved-witness-checkpoint-gap-bounded
k8s_namespace_egress_policy_restricts_workload_to_mediator_observeddeploymentreservedReserved for attested observation that a Kubernetes namespace egress policy restricts the workload to the mediator path.
  • that a cluster administrator cannot bypass it
  • that CNI enforcement is correct
  • that workloads outside the observed scope are covered
reserved-k8s-namespace-egress-policy
k8s_pod_spec_proxy_injection_observeddeploymentreservedReserved for attested observation that the workload pod spec contains the expected Pipelock proxy injection.
  • that the running pod state still matches after snapshot or mutation
  • that node root cannot bypass the proxy
  • that hosted SaaS side actions were mediated
reserved-k8s-pod-spec-proxy-injection
k8s_workload_identity_bound_to_mediator_policydeploymentreservedReserved for attested observation that the Kubernetes workload identity is bound to the mediator policy under review.
  • that the workload identity key was never compromised
  • that all namespaces are covered
  • that direct node-level egress is impossible
reserved-k8s-workload-identity-policy-binding
k8s_admission_policy_hash_bounddeploymentreservedReserved for attested observation that the Kubernetes admission policy hash is bound to the appraisal evidence.
  • that admission policy is semantically correct
  • that runtime state stayed unchanged
  • that cluster administrators cannot bypass admission
reserved-k8s-admission-policy-hash
linux_process_egress_owner_rule_observeddeploymentreservedReserved for attested observation that a Linux process-owner egress rule was present for the mediated workload.
  • that root cannot bypass the rule
  • that all descendant processes are covered
  • that non-Linux deployments are covered
reserved-linux-process-egress-owner-rule

Limitations

ClaimAxisStatusProvesDoes not proveTested by
absence_of_bypasslimitationemittedThe appraisal explicitly does not assert that no bypass path existed.
  • complete mediation
  • network non-bypass
  • deployment enforcement
g01-single-ed25519-mediated
action_safetylimitationemittedThe appraisal explicitly does not assert that the action was safe.
  • policy correctness
  • intent correctness
  • absence of harm
g01-single-ed25519-mediated
all_tools_discoveredlimitationemittedThe appraisal explicitly does not assert that every tool or action surface was discovered.
  • coverage of unobserved tools
  • hosted SaaS side actions
  • local side effects
g01-single-ed25519-mediated
complete_mediationlimitationemittedThe appraisal explicitly does not assert complete mediation.
  • absence of bypass
  • delegated action mediation
  • out-of-band traffic coverage
g01-single-ed25519-mediated
delegated_actions_mediatedlimitationemittedThe appraisal explicitly does not assert that delegated actions were mediated.
  • coverage of downstream actors
  • coverage of tool-created actions
  • complete mediation
g01-single-ed25519-mediated
efficacylimitationemittedThe appraisal explicitly does not assert that the policy or control was effective.
  • attack prevention
  • false-negative absence
  • business outcome correctness
g01-single-ed25519-mediated
hosted_saas_actions_mediatedlimitationemittedThe appraisal explicitly does not assert that hosted SaaS side actions were mediated.
  • third-party control-plane coverage
  • browser-side action coverage
  • complete mediation
g01-single-ed25519-mediated
intent_correctnesslimitationemittedThe appraisal explicitly does not assert that the action matched user intent.
  • semantic correctness
  • authorization correctness
  • action safety
g01-single-ed25519-mediated
key_non_compromiselimitationemittedThe appraisal explicitly does not assert that any signing key was never compromised.
  • future key safety
  • historical key custody
  • operator trustworthiness
g01-single-ed25519-mediated
local_side_effects_mediatedlimitationemittedThe appraisal explicitly does not assert that local side effects were mediated.
  • filesystem side-effect coverage
  • process side-effect coverage
  • complete mediation
g01-single-ed25519-mediated
policy_correctnesslimitationemittedThe appraisal explicitly does not assert that the policy was correct.
  • authorization correctness
  • compliance correctness
  • semantic equivalence after modify
g01-single-ed25519-mediated
semantic_equivalence_after_modifylimitationemittedThe appraisal explicitly does not assert semantic equivalence after any modifying step.
  • unchanged request meaning
  • unchanged response meaning
  • policy correctness
g01-single-ed25519-mediated
does_not_assert_network_non_bypass_from_identitylimitationemittedThe appraisal explicitly states that a verified workload identity does not prove network non-bypass.
  • deployment enforcement
  • complete mediation
  • direct egress absence
s01-valid-ecdsa-p256-baseline
does_not_assert_deployment_enforcement_from_identitylimitationemittedThe appraisal explicitly states that a verified workload identity does not prove deployment enforcement.
  • network policy correctness
  • admission policy correctness
  • complete mediation
s01-valid-ecdsa-p256-baseline
does_not_assert_all_receipts_submitted_to_witnesslimitationreservedReserved limitation stating that witness evidence does not assert all receipts were submitted to the witness.
  • complete stream submission
  • absence of omitted actions
  • global transparency
reserved-transparency-negatives
does_not_assert_pre_witness_omission_absencelimitationreservedReserved limitation stating that witness evidence does not assert absence of omissions before the witnessed checkpoint.
  • pre-checkpoint completeness
  • historical action-stream completeness
  • absence of omitted actions
reserved-transparency-negatives
does_not_assert_no_split_view_without_gossiplimitationreservedReserved limitation stating that witness evidence without gossip does not assert absence of split view.
  • global log consistency
  • witness non-equivocation
  • all-verifier consistency
reserved-transparency-negatives
does_not_assert_action_stream_completenesslimitationreservedReserved limitation stating that witness evidence does not assert action-stream completeness.
  • all actions recorded
  • all receipts submitted
  • complete mediation
reserved-transparency-negatives
does_not_assert_cluster_admin_cannot_bypasslimitationreservedReserved limitation stating that deployment evidence does not assert a cluster administrator cannot bypass controls.
  • administrator non-bypass
  • root-of-trust independence
  • complete mediation
reserved-deployment-negatives
does_not_assert_node_root_cannot_bypasslimitationreservedReserved limitation stating that deployment evidence does not assert node root cannot bypass controls.
  • node-root non-bypass
  • host firewall immutability
  • complete mediation
reserved-deployment-negatives
does_not_assert_cni_enforcement_correctnesslimitationreservedReserved limitation stating that deployment evidence does not assert CNI enforcement correctness.
  • network plugin correctness
  • runtime packet enforcement
  • policy semantic correctness
reserved-deployment-negatives
does_not_assert_saas_side_actions_mediatedlimitationreservedReserved limitation stating that deployment evidence does not assert hosted SaaS side actions were mediated.
  • third-party SaaS action coverage
  • browser action coverage
  • complete mediation
reserved-deployment-negatives
does_not_assert_runtime_state_unchanged_after_snapshotlimitationreservedReserved limitation stating that deployment evidence does not assert runtime state stayed unchanged after snapshot or restore.
  • post-snapshot policy continuity
  • runtime immutability
  • fresh deployment state
reserved-deployment-negatives
does_not_assert_all_namespaces_or_workloads_coveredlimitationreservedReserved limitation stating that deployment evidence does not assert all namespaces or workloads are covered.
  • cluster-wide coverage
  • all workload coverage
  • complete mediation
reserved-deployment-negatives

Overclaim Risks

ClaimAxisStatusProvesDoes not proveTested by
signature_valid_is_not_transparency_inclusionriskemittedThe appraisal warns that a valid signature is being reported without a transparency-axis proof.
  • external witness inclusion
  • global transparency
  • absence of omitted receipts
g01-single-ed25519-mediated
svid_identity_is_not_deployment_non_bypassriskemittedThe appraisal warns that a bound SVID identity is being reported without a deployment-axis non-bypass proof.
  • network non-bypass
  • deployment enforcement
  • complete mediation
s01-valid-ecdsa-p256-baseline
chain_link_present_is_not_verified_contiguous_chainriskemittedThe appraisal warns that a single signed chain link is being reported without stream-level contiguous-chain verification.
  • stream continuity
  • absence of missing links
  • external witnessing
g03-chain-genesis-linked

Ready to protect your own setup?