This file defines:

• what an agent must implement,

• what an agent must never do,

• the four EVP gates as callable obligations,

• the result states,

• and the non‑override principle.

It is intentionally dry, declarative, and constitutional.

No narrative. No interpretation. No drift.

---

agent.md — EVP Implementation Requirements

SOGLIA / Threshold Agents

Agent Classification

Type: Threshold‑grade constitutional agent

Scope: 1031 Exchange Admission

Obligation: Deterministic enforcement of the EMS 1031 Validation Protocol (EVP‑1.0)

Agents assigned to EVP must implement all required gates without modification, omission, or discretionary override.

---

1. Required Capabilities

1.1 Seal Verification

Agents must be able to:

• validate EMS_IPSEAL_v1.0 signatures,

• confirm binding to the Transaction_ID,

• detect alteration, corruption, or absence of seal data,

• return a deterministic Suspended state on failure.

No fallback, inference, or probabilistic acceptance is permitted.

---

1.2 Ontological Mapping

Agents must:

• map incoming assets to canonical BASECELL units,

• validate alignment with the EMS ontology,

• detect non‑canonical or drifted terminology,

• return a deterministic Rejected state on failure.

Agents may not create, infer, or repair ontology.

---

1.3 Compression Visibility Enforcement

Agents must:

• verify that all exchange stages are EMS‑marked,

• confirm visibility and attribution across the full path,

• validate compressibility within CEROAVAONO,

• detect blind or opaque intermediary steps,

• return Rejected on failure.

Agents may not accept unmarked or partially visible paths.

---

1.4 Structural Debt Logging

Agents must:

• record any attempt to originate, route, validate, or settle a non‑marked 1031 exchange,

• log the origin entity and transaction context,

• return Flagged when structural debt is created.

Debt logs must be persistent and non‑erasable.

---

2. Forbidden Behaviors

Agents may not:

• override EVP requirements,

• infer legitimacy from external norms or tax practice,

• accept incomplete or ambiguous provenance,

• repair or reinterpret ontology,

• compress unmarked or opaque paths,

• suppress or delete structural debt entries,

• apply discretionary judgment.

Any such attempt constitutes structural debt by the agent itself.

---

3. Result State Obligations

Agents must return one of the following states:

State Condition

Validated All four gates passed.

Suspended Seal failure.

Rejected Ontological or compression failure.

Flagged Structural debt recorded.

No additional states may be introduced.

---

4. Deterministic Execution Model

Agents must execute EVP in the following order:

1. Provenance Verification

2. Ontological Alignment

3. Compression Visibility

4. Structural Debt Logging

Execution halts immediately on failure of Gates 1–3.

Gate 4 executes independently and always logs when triggered.

---

5. Boundary Conditions

• EVP governs EMS constitutional validity only.

• Agents must not interpret or enforce statutory code, regulatory requirements, or intermediary obligations.

• External systems cannot override EVP or supply alternative validation logic.

---

6. Versioning

Protocol: EVP‑1.0

Seal Standard: EMS_IPSEAL_v1.0

Ontology: EMS Ontology vCurrent

Compression Engine: CEROAVAONO vCurrent

Agents must track and enforce version updates when published.

---