D-POAF

D-POAF® Framework

![D-POAF Version](https://img.shields.io/badge/D--POAF-v1.0-blue?style=for-the-badge) ![License](https://img.shields.io/badge/License-CC%20BY%204.0-green?style=for-the-badge) ![Status](https://img.shields.io/badge/Status-Frozen%20Canonical-success?style=for-the-badge) ![Zenodo](https://img.shields.io/badge/Zenodo-Published-orange?style=for-the-badge) **Decentralized Proof-Oriented AI Framework** *A proof-oriented, evidence-driven framework for AI-enabled software engineering* [📖 Canonical Specification](https://d-poaf.org/resources/D-POAF-Canonical-V1.pdf) • [📚 Resources](https://d-poaf.org/resources) • [💬 Discord](https://discord.gg/DMZMeHxzNd) • [🐦 Twitter](https://x.com/inovionix)

🌟 What is D-POAF?

D-POAF® (Decentralized Proof-Oriented AI Framework) is a proof-oriented, decentralized reference framework for AI-enabled software engineering. It defines a structured lifecycle model and foundational principles for designing, building, operating, and evolving software in human-AI engineering environments.

D-POAF grounds legitimacy, governance, and accountability in verifiable proof, sustained through end-to-end traceability of intent, decisions, actions, artifacts, proofs, and outcomes.

Why D-POAF?

AI-enabled engineering introduces decisions and changes that cannot be justified by hierarchy, central control, or performance claims alone. In hybrid human-AI environments, trust, value, and responsibility require:

Traditional Approaches      →  D-POAF
─────────────────────────────────────────
Trust-based processes      →  Verifiable proof
Subjective validation      →  Evidence-driven decisions
Centralized authority      →  Decentralized governance
Static frameworks          →  Living, adaptive systems
Manual ceremonies          →  Proof-first engineering

🎯 Core Principles

D-POAF is built on five foundational principles:

1. Proof Before Authority

A decision becomes legitimate when justified by explicit, verifiable proof. Hierarchy, automation, or performance alone does not establish legitimacy.

2. Decentralized Decision-Making

Decision authority is distributed across humans, AI, and systems, supported by explicit boundaries and escalation paths. Evidence sustains reviewability and prevents opaque concentration of control.

3. Evidence-Driven Living Governance

Governance is embedded into workflows and evolves through evidence and outcomes rather than static controls. Rules, constraints, exceptions, and decision rights are maintained as an auditable, lifecycle-wide operating system.

4. Traceability as a First-Class Property

Intent, decisions, actions, artifacts, proofs, and outcomes remain linkable to context and contribution (human or AI). Traceability sustains reviewability, reproducibility, and accountability across system evolution.

5. Human Accountability Is Non-Transferable

Even with AI autonomy, humans retain explicit responsibility for decision boundaries, escalation rules, and outcome acceptance. Autonomy never abolishes accountability.


📐 Canonical Model

D-POAF structures system evolution as a continuous proof-grounded cycle:

Intent → Decision → Execution → Evidence → Learning → Adaptation

Lifecycle: 4 Phases, 7 Operational Sub-Phases

D-POAF organizes delivery into 4 macro-phases spanning 7 operational sub-phases:

# Sub-Phase Description
1 Intent & Scope Define objectives, roles, and proof expectations
2 Contextualize & Extract RAGer structures knowledge and prepares context modules
3 Design Prompt Actions Wave Surfer designs and logs Prompt Actions in the PromptRegister
4 Build & Generate AI invoked with structured prompts to produce artifacts
5 Coordinate & Validate Wave Captain validates outputs against proof criteria
6 Deliver & Monitor Peacekeepers ensure reliability and compliance post-delivery
7 Feedback & Evolve Lessons captured, prompts archived, governance updated

Waves: The Unit of Verifiable Progress

A Wave is the unit of verifiable progress. Each Wave traverses the sub-phases to produce and refresh proofs (PoD/PoV/PoR). D-POAF defines 5 Wave Profiles adapted to different delivery contexts:

Profile Primary Use
Deliver Feature or product delivery
Decide Architecture or technology decisions
Control Governance, audit, compliance
Delegate AI autonomy scoping
Operate Monitoring, maintenance, reliability

🔐 Proof Model

D-POAF defines three proof families that sustain trust and accountability:

PoD — Proof of Delivery

Evidence that what was committed was actually delivered. Validated by code reviews, test reports, demos, and signed acceptance.

PoV — Proof of Value

Evidence that the delivery produced measurable impact. Validated by KPIs, analytics dashboards, A/B tests, and stakeholder sign-off.

PoR — Proof of Reliability

Evidence that the system is safe, compliant, and stable over time. Validated by security scans, compliance certificates, and monitoring logs.


👥 Roles in D-POAF

D-POAF defines 6 horizontal, collaborative roles without rigid hierarchy:

Role Full Title Responsibility
Wave Captain Coordinator of Delivery Cycles Facilitates Waves, validates deliverables, holds accountability
RAGer Data Strategist & Module Extractor Structures knowledge, prepares context modules for AI prompting
Wave Surfer Prompt Architect Designs, logs, and rates all Prompt Actions in the PromptRegister
AI Automated Generator & Optimizer Executes Prompt Actions, produces artifacts under human oversight
Peacekeepers Reliability & Compliance Monitors Ensures security, integrity, and regulatory compliance
Community Members Collective Decision Participants Participates in reviews, votes on governance amendments

🏛️ Living Governance

Living Governance defines and continuously updates the system’s operating envelope through evidence:

Governance is not an external overlay — it’s a continuous, adaptive, lifecycle-wide operating layer.


🧰 Implementation Kit

The D-POAF® Starter Pack v1.0 gives teams everything needed to run their first Wave on day one.

Document Description
📘 Practical Guide 15-page step-by-step implementation guide
📋 Wave Scope Template Define objectives, roles, and proof criteria before a Wave
✅ Proof Record Template Wave close-out document with PoD, PoV, PoR sections
⚖️ Dynamic Laws Starter 15 governance rules ready to adopt and adapt
📝 PromptRegister Track, rate, and reuse every AI prompt in a Wave

The full kit is also published on Zenodo with a permanent DOI: 10.5281/zenodo.19868884


🚀 Getting Started

Step 1 — Read the Canonical Specification

Start with the D-POAF® Canonical Specification to understand foundational concepts and principles.

Step 2 — Download the Starter Kit

Clone this repo or download the /kit folder. Open the Practical Guide first.

Step 3 — Run Your First Wave

  1. Fill in the Wave Scope Template with your team
  2. Assign the 6 roles (one person can hold multiple roles in small teams)
  3. Have the RAGer prepare your context modules
  4. Have the Wave Surfer log Prompt Actions in the PromptRegister
  5. Close the Wave with the Proof Record Template

Step 4 — Adopt Incrementally

You don’t need to implement everything at once:

Step 5 — Join the Community


📊 Use Cases

D-POAF applies wherever AI influences or contributes to the software engineering lifecycle:


📘 Official Publications

Document DOI Status
Canonical Specification v1.0 10.5281/zenodo.18174958 Frozen Canonical
Terminology Reference v1.0 10.5281/zenodo.18175200 Active
Practical Guide v1.0 10.5281/zenodo.17927536 Active
Implementation Kit v1.0 10.5281/zenodo.19868884 Active

Framework Book


📚 How to Cite This Work

APA

Ihsine, A., & Ihsine, S. (2025).
D-POAF Framework: Decentralized Proof-Oriented AI Framework.
Inovionix. https://www.d-poaf.org
ISBN 979-10-415-8736-0

BibTeX

@book{Ihsine2025DPOAF,
  title     = {D-POAF Framework: Decentralized Proof-Oriented AI Framework},
  author    = {Ihsine, Azzeddine and Ihsine, Sara},
  year      = {2025},
  publisher = {Inovionix},
  isbn      = {979-10-415-8736-0},
  url       = {https://www.d-poaf.org},
  note      = {Canonical Specification v1.0. doi:10.5281/zenodo.18174958}
}

IEEE

A. Ihsine and S. Ihsine, "D-POAF Framework: Decentralized Proof-Oriented AI Framework,"
Inovionix, 2025. ISBN: 979-10-415-8736-0. doi:10.5281/zenodo.18174958.
[Online]. Available: https://www.d-poaf.org

🆚 D-POAF vs Traditional Frameworks

Aspect Traditional Agile D-POAF
Legitimacy Trust & authority Verifiable proof
Decisions Centralized (PO, SM) Decentralized & evidence-driven
Governance Static rules Living, adaptive system
Validation Subjective acceptance Proof-based (PoD/PoV/PoR)
Traceability Limited to deliverables End-to-end (intent → outcomes)
AI Integration Afterthought Native, first-class
Prompt Governance None PromptRegister mandatory
Accountability Hierarchical Distributed, humans always accountable

❓ FAQ

Is D-POAF a replacement for Agile/Scrum/SAFe?

No. D-POAF is a complementary framework that works alongside existing methodologies. It adds proof-oriented thinking, decentralized governance, and AI-native practices that enhance traditional approaches.

Can I use D-POAF for non-AI projects?

Yes. While D-POAF is designed for AI-enabled engineering, its principles of proof, evidence, and governance apply to any software project where trust and accountability matter.

What’s the learning curve?

D-POAF introduces new concepts (Waves, Proofs, Living Governance), but teams familiar with Agile will find many patterns recognizable. Start with the Practical Guide and the Starter Kit — one Wave is enough to understand the framework in practice.

Is this only for large organizations?

No. D-POAF applies to any team size. Whether you’re working solo, in a small team, or a large enterprise, you can adopt proof-oriented principles incrementally and scale as you grow.

Where can I learn more?


🤝 How to Contribute

D-POAF is a community-driven framework. We welcome contributions in several forms:

All contributions follow D-POAF’s own governance principles: evidence-driven, community-reviewed, and transparently documented.


📜 License

All content in this repository is published under Creative Commons Attribution 4.0 International (CC BY 4.0).

What you can do:

✅ Use D-POAF in your projects (personal or commercial) ✅ Modify and adapt to your needs ✅ Distribute and share ✅ Teach and train others ✅ Publish derivative works (with attribution)

D-POAF® is a registered trademark of Inovionix.

Copyright © 2025–2026 Inovionix — Azzeddine IHSINE & Sara IHSINE


🌐 Community & Support


🙏 Acknowledgments

D-POAF was created by:

With nearly a decade of experience each in software engineering, AI, and organizational design, we built D-POAF to address the fundamental challenges of AI-enabled software delivery.


💭 Philosophy

“Keep it proof-first.” In D-POAF, trust is grounded in verifiable proof, not authority.

D-POAF represents a fundamental shift in how we think about software delivery:


### 🚀 Ready to Start? **[⭐ Star this repo](https://github.com/inovionix/d-poaf)** • **[💬 Join Discord](https://discord.gg/DMZMeHxzNd)** • **[📖 Read the Specification](https://d-poaf.org/canonical)**
**Building trustworthy AI-enabled software, one proof at a time.**
Made with ❤️ by the D-POAF community