NOC Problem Statements (NPS)

NOC NPS documents describe known limitations, open challenges, or architectural issues in the NOC platform.
They are maintained by the NOC core team as a way to track and prioritize problems that may inspire future enhancements or NEPs.

Each NPS defines a problem in clear, technical terms and is used to focus discussion, inform planning, and document why certain changes may be necessary.

NPS Workflow

The NPS process follows these stages:

1. 📝 Draft — A new NEP is written and submitted as a draft, typically as a pull request.
2. 💬 Discussion — The NEP is reviewed, discussed, and possibly revised.
3. ✅ Accepted — Once consensus is reached, the NEP is approved and marked as Accepted.
4. 🛠️ In Progress — The NEP has been accepted and is currently being implemented.
5. ❌ Rejected — NEPs that are not approved are marked as Rejected.
6. 🚀 Done — NEPs that have been fully implemented and deployed may be marked as Done.

stateDiagram-v2
    draft: 📝 Draft
    discussion: 💬 Discussion
    accepted: ✅ Accepted
    inprogress: 🛠️ In Progress
    rejected: ❌ Rejected
    done: 🚀 Done
    [*] --> draft
    draft --> discussion
    discussion --> draft
    draft --> rejected
    discussion --> accepted
    discussion --> rejected
    accepted --> inprogress
    inprogress --> done

Index of NPS

NPS	Title	Author	Status

📝 Draft: 0 ❌ Rejected: 0 💬 Discussion: 0 🚀 Done: 0 ✅ Accepted: 0 🛠️ In Progress: 0