# Project Admission Template

## Identity

- **Project ID:**
- **Canonical name:**
- **Slug:**
- **Lifecycle state:** `proposed` or `incubating`
- **Steward/handoff role:**

## Engineering relationship

Describe why this effort belongs within Project Frankenstein and which existing
firmware, media, hardware, emulator, tooling, or preservation domains it serves.

## Scope

### Included

- 

### Explicit non-goals

- 

## Current artifacts

| Artifact | Size | SHA-256 | Role | Integrity status |
|---|---:|---|---|---|
| | | | | |

## Maturity

- current revision or baseline;
- validated capabilities;
- unvalidated assumptions;
- known safety boundaries;
- current hold points.

## Gates

| Gate | State | Evidence or remaining requirement |
|---|---|---|
| Project admission | | |
| Repository readiness | | |
| Authority activation | | |
| Hardware fabrication release, when applicable | | |
| Destructive-operation authorization, when applicable | | |

## Repository decision

State whether a repository is not requested, deferred, under review, staged, or
active. Explain the boundary and why the current state is appropriate.

## Next accepted actions

1. 

## Prohibited or deferred actions

- 

## Handoff

Identify the canonical PFES record and the exact current source artifact that a
new engineer or agent must receive.
