opencode-skills-collection 4.1.2 → 4.1.4

package/bundled-skills/smart-contract-formal-verification/SKILL.md

@@ -0,0 +1,136 @@
+---
+name: smart-contract-formal-verification
+description: 'Foundry and Soroban formal invariant verification register: state transition rules, boundary invariant properties, and symbolic execution checks.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [formal-verification, invariants, foundry, soroban, security, math]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Smart Contract Formal Verification
+
+**What it is:** Applies rigorous mathematical invariant proofs, symbolic execution engines, and property-based fuzz tests to verify smart contract safety.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Smart Contract Formal Verification** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Smart Contract Formal Verification.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | Formal Spec ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `SPEC-001` |
+| 2 | Target Contract Module | `text` | `VARCHAR(64)` | `string` | Text | `vault_liquidity_engine` |
+| 3 | State Transition Property | `text` | `VARCHAR(128)` | `string` | Text | `Total Assets Equals Sum of Shares` |
+| 4 | Verification Method | `select` | `VARCHAR(64)` | `string` | Select | `Foundry Invariant Fuzzing` |
+| 5 | Fuzz Runs Count | `number` | `INTEGER` | `number` | Number | `100000` |
+| 6 | Symbolic Execution Engine | `select` | `VARCHAR(32)` | `string` | Select | `Certora Prover` |
+| 7 | Counterexample Discovered | `select` | `VARCHAR(16)` | `string` | Select | `No` |
+| 8 | Mathematical Theorem Proved | `select` | `VARCHAR(16)` | `string` | Select | `Yes` |
+| 9 | Invariant Violation Tolerance | `currency` | `NUMERIC(14,2)` | `number` | Number | `0.00` |
+| 10 | Formal Verification Status | `select` | `VARCHAR(32)` | `string` | Select | `Formally Verified` |
+| 11 | Proof Generation Date | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**Verification Method**
+
+```
+Foundry Invariant Fuzzing | Halmos Symbolic Execution | Certora Rule Prover | SMT Solver
+```
+
+**Symbolic Execution Engine**
+
+```
+Certora Prover | Halmos | Z3 SMT | None (Fuzzing Only)
+```
+
+**Counterexample Discovered**
+
+```
+Yes | No
+```
+
+**Mathematical Theorem Proved**
+
+```
+Yes | No
+```
+
+**Formal Verification Status**
+
+```
+Formally Verified | Violations Found | Proof In Progress
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Smart Contract Formal Verification for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
+- @web3-rate-limiting-circuit-breaker - provides operational guardrails and threshold breakers.
+- @cross-chain-relayer-audit - covers message hashes, nonces and quorum proofs.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Smart Contract Formal Verification register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```

package/bundled-skills/smart-contract-upgrade-governance/SKILL.md

@@ -0,0 +1,130 @@
+---
+name: smart-contract-upgrade-governance
+description: 'Soroban WASM upgrade governance register: executable bytecode hash, timelocked migration delays, and multi-sig authorization quorum.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [soroban, upgrade, governance, security, wasm, stellar]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Smart Contract Upgrade Governance
+
+**What it is:** Enforces deterministic timelocks, cryptographic bytecode hash verification, and multi-sig consensus for non-custodial smart contract upgrades.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Smart Contract Upgrade Governance** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Smart Contract Upgrade Governance.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | Upgrade Proposal ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `UPG-001` |
+| 2 | Target Contract Address | `text` | `VARCHAR(56)` | `string` | Text | `CAUD...` |
+| 3 | New WASM Bytecode Hash | `text` | `VARCHAR(64)` | `string` | Text | `e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855` |
+| 4 | Timelock Delay Hours | `number` | `INTEGER` | `number` | Number | `48` |
+| 5 | Governance Quorum Required | `select` | `VARCHAR(32)` | `string` | Select | `3-of-5 Multisig` |
+| 6 | State Migration Function | `text` | `VARCHAR(64)` | `string` | Text | `migrate_storage_v2` |
+| 7 | Emergency Cancel Permitted | `select` | `VARCHAR(16)` | `string` | Select | `Yes` |
+| 8 | Audit Certification Attached | `select` | `VARCHAR(16)` | `string` | Select | `Yes` |
+| 9 | Upgrade Lifecycle Status | `select` | `VARCHAR(32)` | `string` | Select | `Timelock Pending` |
+| 10 | Authorized Proposer | `text` | `VARCHAR(56)` | `string` | Text | `GPROP...` |
+| 11 | Proposal Submission Date | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**Governance Quorum Required**
+
+```
+3-of-5 Multisig | 4-of-7 Multisig | DAO Token Vote Quorum
+```
+
+**Emergency Cancel Permitted**
+
+```
+Yes | No
+```
+
+**Audit Certification Attached**
+
+```
+Yes | No
+```
+
+**Upgrade Lifecycle Status**
+
+```
+Draft | Timelock Pending | Executed | Cancelled Revoked
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Smart Contract Upgrade Governance for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
+- @smart-contract-formal-verification - verifies state invariants mathematically.
+- @stellar-multisig-threshold-coordinator - covers signer weights and threshold coordination.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Smart Contract Upgrade Governance register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```

package/bundled-skills/soroban-contract-audit/SKILL.md

@@ -0,0 +1,136 @@
+---
+name: soroban-contract-audit
+description: 'Soroban smart contract security audit register: authorization checks, panic pathways, integer overflows, and storage footprint verification for Stellar.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [stellar, soroban, rust, smart-contracts, security, audit, web3]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Soroban Contract Security Audit
+
+**What it is:** Tracks formal security audit findings, authorization invariants, and WASM storage footprint compliance for Soroban Rust smart contracts on Stellar.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Soroban Contract Security Audit** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Soroban Contract Security Audit.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | Audit Finding ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `AUD-001` |
+| 2 | Contract Address | `text` | `VARCHAR(56)` | `string` | Text | `CA3D5K...` |
+| 3 | Function Name | `text` | `VARCHAR(64)` | `string` | Text | `transfer_with_approval` |
+| 4 | Severity Tier | `select` | `VARCHAR(32)` | `string` | Select | `High` |
+| 5 | Vulnerability Class | `select` | `VARCHAR(64)` | `string` | Select | `Missing Auth Check` |
+| 6 | Storage Footprint Type | `select` | `VARCHAR(32)` | `string` | Select | `Persistent` |
+| 7 | Panic Pathway Present | `select` | `VARCHAR(16)` | `string` | Select | `Yes` |
+| 8 | PoC Test Case | `text` | `VARCHAR(255)` | `string` | Text | `test_unauthorized_state_drain` |
+| 9 | Remediation Status | `select` | `VARCHAR(32)` | `string` | Select | `Remediated` |
+| 10 | Auditor Lead | `text` | `VARCHAR(64)` | `string` | Text | `Ranjeet2063` |
+| 11 | Verification Date | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**Severity Tier**
+
+```
+Critical | High | Medium | Low | Informational
+```
+
+**Vulnerability Class**
+
+```
+Missing Auth Check | Integer Overflow | Storage Desync | Reentrancy Variant | Unbounded Loop | Gas Exhaustion
+```
+
+**Storage Footprint Type**
+
+```
+Instance | Persistent | Temporary
+```
+
+**Panic Pathway Present**
+
+```
+Yes | No
+```
+
+**Remediation Status**
+
+```
+Identified | In Progress | Remediated | Risk Accepted
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Soroban Contract Security Audit for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @smart-contract-formal-verification - verifies state invariants mathematically.
+- @soroban-liquidity-pool - covers AMM invariant and LP-share modelling.
+- @soroban-token-minter - covers SEP-41 token supply, admin and event modelling.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Soroban Contract Security Audit register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```

package/bundled-skills/soroban-liquidity-pool/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: soroban-liquidity-pool
+description: 'Automated market maker liquidity pool register: constant-product invariant curves, swap fee tiers, and LP token shares for Soroban DeFi.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [soroban, amm, liquidity, stellar, dex, defi, rust]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Soroban Liquidity Pool Architecture
+
+**What it is:** Tracks automated market maker (AMM) liquidity pools, mathematical invariant boundaries, and token reserve ratios on Soroban DeFi networks.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Soroban Liquidity Pool Architecture** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Soroban Liquidity Pool Architecture.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | Pool Pair ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `POOL-001` |
+| 2 | Token A Contract | `text` | `VARCHAR(56)` | `string` | Text | `CASWAP1...` |
+| 3 | Token B Contract | `text` | `VARCHAR(56)` | `string` | Text | `CASWAP2...` |
+| 4 | Invariant Model | `select` | `VARCHAR(32)` | `string` | Select | `Constant Product (xy=k)` |
+| 5 | Fee Basis Points | `number` | `INTEGER` | `number` | Number | `30` |
+| 6 | Token A Reserve | `currency` | `NUMERIC(24,7)` | `number` | Number | `250000.0000000` |
+| 7 | Token B Reserve | `currency` | `NUMERIC(24,7)` | `number` | Number | `125000.0000000` |
+| 8 | Total LP Shares Issued | `currency` | `NUMERIC(24,7)` | `number` | Number | `176776.6952966` |
+| 9 | Slippage Tolerance Bps | `number` | `INTEGER` | `number` | Number | `50` |
+| 10 | Pool Health Status | `select` | `VARCHAR(32)` | `string` | Select | `Balanced` |
+| 11 | Last Rebalance Date | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**Invariant Model**
+
+```
+Constant Product (xy=k) | StableSwap Curve | Concentrated Liquidity
+```
+
+**Pool Health Status**
+
+```
+Balanced | Impermanent Divergence | High Volatility | Frozen
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Soroban Liquidity Pool Architecture for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
+- @soroban-token-minter - covers SEP-41 token supply, admin and event modelling.
+- @web3-rate-limiting-circuit-breaker - provides operational guardrails and threshold breakers.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Soroban Liquidity Pool Architecture register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```

package/bundled-skills/soroban-oracle-data-feed-audit/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: soroban-oracle-data-feed-audit
+description: 'DeFi price oracle integration and safety audit register: heartbeat bounds, stale price threshold reversion, and TWAP medianizer validation.'
+category: engineering
+risk: safe
+source: self
+source_type: self
+date_added: "2026-10-01"
+author: Ranjeet2063
+tags: [soroban, oracle, defi, pricing, stellar, security, web3]
+tools: []
+source_repo: Ranjeet2063/agentic-awesome-skills
+---
+
+# Soroban Oracle Data Feed Audit
+
+**What it is:** Tracks decentralized price feed providers, staleness boundaries, and multi-source medianizer logic to prevent oracle manipulation in Soroban protocols.
+
+## Overview
+
+Provides a standardized, auditable framework and data model for **Soroban Oracle Data Feed Audit** operations across distributed engineering and decentralized application systems.
+
+## When to Use This Skill
+
+- When formalizing architectural contracts, security invariants, or operational limits for Soroban Oracle Data Feed Audit.
+- When cross-functional review is required between protocol developers, smart contract auditors, and AI engineering agents.
+- When generating reproducible CSV, SQL DDL, JSON Schema, and Notion property registers for tracking compliance.
+
+## How It Works
+
+1. Define the parameters, thresholds, and identity bindings required for the target operational register.
+2. Select appropriate boundary enforcement values from validated enum select sets.
+3. Export standardized artifacts (CSV table, SQL DDL, JSON Schema) to integrate into validation CI pipelines.
+
+## Field Reference
+
+| # | Field Name | Type | SQL Type | JSON Schema Type | Notion Property Type | Example Value |
+|---|------------|------|----------|------------------|----------------------|---------------|
+| 1 | Oracle Feed ID | `id` | `SERIAL PRIMARY KEY` | `integer` | Text | `ORC-001` |
+| 2 | Asset Pair Identifier | `text` | `VARCHAR(32)` | `string` | Text | `XLM/USD` |
+| 3 | Oracle Contract Address | `text` | `VARCHAR(56)` | `string` | Text | `CORC...` |
+| 4 | Max Stale Period Seconds | `number` | `INTEGER` | `number` | Number | `300` |
+| 5 | Deviation Threshold Bps | `number` | `INTEGER` | `number` | Number | `100` |
+| 6 | TWAP Window Length Seconds | `number` | `INTEGER` | `number` | Number | `1800` |
+| 7 | Medianizer Minimum Sources | `number` | `INTEGER` | `number` | Number | `3` |
+| 8 | Circuit Breaker Reversion Bound | `select` | `VARCHAR(16)` | `string` | Select | `Yes` |
+| 9 | Feed Health Status | `select` | `VARCHAR(32)` | `string` | Select | `Active Healthy` |
+| 10 | Last Reported Price | `currency` | `NUMERIC(18,7)` | `number` | Number | `0.1250000` |
+| 11 | Audit Verification Date | `date` | `DATE` | `string, format: date` | Date | `2026-10-01` |
+
+## Select Options
+
+**Circuit Breaker Reversion Bound**
+
+```
+Yes | No
+```
+
+**Feed Health Status**
+
+```
+Active Healthy | Stale Alert | Deviation Triggered | Paused
+```
+
+## Relations
+
+- `Audit Reference` -> links to the formal review documentation or test repository.
+- `Target Architecture` -> links to the deployed contract or autonomous agent runtime component.
+
+## Examples
+
+**Prompt**
+
+```
+How do I configure and track Soroban Oracle Data Feed Audit for our production environment?
+```
+
+**Recommended Next Step**
+
+> Generate the unified field schema, SQL DDL migration, and JSON validation schema to register into your system catalog.
+>
+> Workflow: Define criteria -> Run automated verification -> Record baseline -> Monitor invariants.
+
+## Best Practices
+
+- Enforce strict typing on numerical bounds and currency amounts; avoid unstructured free-text fields for critical states.
+- Re-run validation test suites on every state-altering commit or parameter change.
+- Keep example data synthetic and isolated from production cryptographic keys or private endpoints.
+
+## Limitations
+
+- Provides architectural specifications, data models, and verification schemas; does not execute direct transaction signing without authorized external tooling.
+- Requires network connectivity and valid RPC credentials when querying on-chain states.
+
+## Security & Safety Notes
+
+- All parameters declare `risk: safe`. No unauthorized state modification or privileged credential access is performed.
+- Use synthetic dummy keys and mock addresses in test suites and local verification scripts.
+
+## Common Pitfalls
+
+- **Problem:** Mismatched decimal precision between contract runtime and database register.
+  **Solution:** Always verify decimals using the explicit field mapping in this reference.
+- **Problem:** Missing authorization checks prior to state update.
+  **Solution:** Cross-validate against the Security Audit register before deployment.
+
+## Related Skills
+
+- @soroban-contract-audit - provides the security checklist and vulnerability categorization.
+- @soroban-storage-ttl-lifecycle - covers ledger rent and TTL extension policy.
+- @smart-contract-formal-verification - verifies state invariants mathematically.
+
+## Reusable Prompt
+
+```
+I want to establish a verified Soroban Oracle Data Feed Audit register for our production protocol.
+Guide me through the required field parameters and output the corresponding SQL DDL and JSON Schema.
+```