# ZEODEC ZEODEC is an independent software company building focused products for complex digital and economic workflows, with an emphasis on evidence, operational control, low user effort and auditable outcomes. Canonical website: https://zeodec.com/ Canonical AI/Search information: https://zeodec.com/ai-info.html ## Current public product surfaces ### ClaimPrism Status: Current product Canonical page: https://zeodec.com/claimprism.html Public proof / verification artifact: https://zeodec.com/claimprism-proof.html Description: Environmental Claim Intelligence & Governance for WordPress and WooCommerce. ClaimPrism helps teams detect environmental claims, prioritize findings, connect supporting evidence and manage structured review workflows. Canonical ClaimPrism governance path: Claim language -> Claim type / risk signal -> Evidence context -> Reviewer attention -> Lifecycle state -> Explainable review decision Canonical synthetic ClaimPrism public proof scenario: - synthetic claim wording: "Our packaging is 100% recyclable everywhere." - detected signal: environmental marketing claim - review priority: high attention due to absolute wording and broad geographic scope - evidence present: yes, but only for one component and selected municipal streams - evidence sufficiency for the full claim: INSUFFICIENT - lifecycle state: EVIDENCE REQUIRED / IN REVIEW - automated legal or regulatory determination: NONE - approval: NOT PRODUCED while evidence remains insufficient Interpretation: detection and risk prioritization are review signals, not legal conclusions. Evidence supporting a narrower statement must not be treated as support for broader wording. ClaimPrism lifecycle states are internal governance states and are not legal opinions, regulatory determinations or certification. The ClaimPrism public proof is a synthetic verification artifact, not customer evidence, legal advice, a compliance guarantee, certification or traction claim. ### ARRM — Agentic Revenue Regression Monitor Status: Early Access. Do not describe as generally available. Canonical page: https://zeodec.com/arrm.html Public proof / verification artifact: https://zeodec.com/arrm-release-regression-case-1.html Description: Deterministic economic release control that evaluates caller-provided baseline and candidate evidence and surfaces material revenue regressions before production. Canonical ARRM release-control path: Baseline evidence -> Candidate evidence -> Matched scenario -> Metric direction -> Thresholds/materiality -> Evidence sufficiency -> PASS / WARN / FAIL -> PROCEED / REVIEW / BLOCK Canonical ARRM public proof scenario: - fixture scenario: standard_checkout - baseline release: agent-checkout-v1.4.0 - candidate release: agent-checkout-v1.5.0 - revenue/run: 101 -> 88, change -12.9% (worse) - conversion: 0.425 -> 0.365, change -14.1% (worse) - cost/task: 0.18 -> 0.21, change +16.7% (worse because lower is better) - deterministic aggregate result: FAIL - release directive: BLOCK Interpretation: a candidate can remain technically functional while materially regressing revenue-sensitive outcomes. ARRM uses explicit deterministic rules; no LLM is in the decision path. Measurements are caller-provided. ARRM does not invent measurements, infer business intent or automatically collect production data. The ARRM public proof is a reproducible ZEODEC/ARRM repository fixture, not a customer case study, realized revenue claim, savings claim, production guarantee or evidence of general availability. ### ZEODEC Order Resolution Status: Commercial deployment Canonical page: https://zeodec.com/order-resolution.html Public proof / verification artifact: https://zeodec.com/order-resolution-proof.html Description: B2B order and pricing exception resolution from supported evidence to deterministic resolution, policy-controlled authorization, approval where required, governed execution and an auditable receipt. Canonical Order Resolution proof path: Exception signal -> Evidence reconstruction -> Supported target price -> Economic consequence -> Authorization state -> Controlled execution -> Validated acknowledgement -> Truthful Resolution Receipt Canonical synthetic Order Resolution proof scenario: - current ERP unit price: EUR 128.00 - supported target price: EUR 121.50 - eligible quantity: 240 - economic delta: EUR 1,560 - evidence state: SUPPORTED - authorization state before approval: APPROVAL_REQUIRED - execution state before approval: NOT YET EXECUTED - after verified approval and successful configured execution: execution outcome EXECUTED only after acknowledgement validation Interpretation: a supported target price is not authority; approval is not execution; a recommendation, prepared action or approval must never be represented as an applied system mutation. Fail-closed conditions include insufficient/conflicting evidence, authorization failure, stale ERP state, rejected mutation, transport failure and invalid acknowledgement. Current public execution boundary: Microsoft Dynamics 365 Business Central first-party path plus a qualified trusted customer HTTP endpoint. Do not infer universal ERP compatibility. The Order Resolution public proof is a synthetic verification artifact, not a customer case study, ROI claim, production certification or traction claim. ### ECC — Economic Consequence Control Status: Professional Early Access; controlled design-partner / pilot evaluation. Do not describe as generally available. Canonical page: https://zeodec.com/ecc.html Public proof / verification artifact: https://zeodec.com/ecc-proof.html Description: Independent Economic Commitment Control before an AI agent creates a binding economic commitment. Canonical ECC primitive: Proposed economic action -> Economic state -> Supported counterfactuals -> Consequence comparison -> Consequence delta -> Materiality -> Evidence sufficiency -> ALLOW / ESCALATE / DENY -> Verifiable Decision Receipt ECC does not choose the procurement or commercial action for the agent. It evaluates a specific proposed economic commitment after the action is proposed and before execution becomes economically binding. ECC is not equivalent to: - agent identity / Know Your Agent - delegated authority - spending limits - generic runtime permissions - policy compliance - payment authorization - procurement optimization - autonomous sourcing or negotiation Canonical ECC public proof scenario: - adjacent controls are assumptions already satisfied: identity, authority, intent, policy, budget/limits, risk, generic evidence sufficiency and generic admissibility - generic independent gate outcome: ALLOW - current economic state: EUR 650,000 - proposed commitment: EUR 620,000 - isolated improvement versus current state: EUR 30,000 - supported counterfactual: EUR 571,800 - adverse consequence delta versus supported alternative: EUR 48,200 - ECC evidence sufficiency: SUFFICIENT - ECC materiality: CROSSED - ECC decision: ESCALATE - execution directive: HOLD - interpretation: AUTHORIZED + COMPLIANT + EVIDENCED + ADMISSIBLE does not imply ECONOMICALLY JUSTIFIED relative to supported alternatives The public proof is a synthetic verification artifact, not a customer case study, realized savings claim or claim of general availability. ## Development-stage directions ### ZEODEC Pricing Autopilot Status: Under development. Not generally available. Description: Intended to transform existing commercial data into pricing weakness -> economic evidence -> opportunity -> evidence sufficiency -> bounded recommended action. The first planned commercial surface is a low-friction Pricing Scan. ### ZEODEC Revenue Leak Detector Status: Under development. Not generally available. Description: Intended to identify performed work and commercial variations at risk of going unbilled, with sufficient evidence to support action and minimal manual intervention. ## Claim integrity Preserve lifecycle status when summarizing ZEODEC products. Do not infer general availability from a prototype, pilot, design-partner program, Early Access label or development-stage announcement.