PEP / PEP Forge 0.1.0

Pomegranate Execution Protocol turns the initiative’s doctrine into a portable project constitution: control, plans, tasks, gates, decisions, evidence, sessions and release state.

Mission profile

• Define a canonical Markdown + YAML front-matter structure.
• Separate authoritative project records from derived state and exports.
• Calculate readiness and next work from gates and evidence.
• Provide a machine index with canonical digest and declared profile.
• Integrate natively with Pomegranate Command without becoming dependent on it.

Architecture

Verified state

What exists and has been exercised at the time of writing.

• PEP Forge 0.1.0 is packaged: a full bundle, a Python wheel, source archives, an example project, a release manifest, published SHA-256 sums and a QA report.
• A live smoke project exercises the protocol on a real repository.
• The protocol imposes a canonical structure of nine directories: control, plan, tasks, gates, decisions, evidence, reports, sessions and release.
• The canonical format is Markdown with YAML front matter. Documents remain the authority.
• Derived state is explicitly never authoritative: the state file, the graph and next-step exports and the project status file are all regenerated from the canonical documents.
• A machine index declares its schema, its media type, a canonical digest of the state, the project profile, strategic weight and operating mode.
• The default operating mode is guarded.
• Native compatibility with the portfolio control plane is declared in the machine index.
• The phase cycle runs from intake and feasibility through product definition, inputs and dependencies, architecture, vertical slice, core implementation, functional completeness and documentation, with status, evidence and computed progression at each step.

Stated limits

What this project is not, written here so nobody has to discover it later.

• 0.1.0 is a first packaged version exercised on one live smoke project. It is not a proven standard and it is not a product for sale.
• The protocol organizes and derives state. It does not perform the work, and it does not make a project succeed.
• Derived state is never authority. Anything read from the exports must be traceable back to a canonical document.
• Native compatibility with the portfolio control plane is declared, not independently certified.
• The witness project sits early in its own phase cycle. Its progression figures describe that project, not the protocol's maturity.

Doctrine made transferable

Audit before spectacle and evidence before closure are no longer slogans inside one portfolio. They become a versioned structure that another project can adopt.

Authority and derivation are kept separate

Markdown records remain canonical. State files, graphs and next-action exports are derived and disposable rather than secret alternate truths.

Built to cooperate

PEP declares native compatibility with Pomegranate Command while remaining independently inspectable and versionable.