Inputs
- Authenticated operator session
- Upstream read routes
Extended platform
NiGeNje Console
A development operator surface.
Same-origin backend-for-frontend operator read surfaces with permission checks and no token leakage. Development/demo surface, not a production operator plane.
Responsibility
What NiGeNje Console is responsible for
The Console is an authenticated operator surface backed by a same-origin backend-for-frontend. It proxies control-plane, admission, AIOps and network read routes with permission checks, and deliberately provides no open proxy and no token leakage to the browser.
Governance needs a place to look. The Console is that surface: a same-origin backend-for-frontend in front of Control Plane, admission, AIOps and other read models, with permission checks at the proxy boundary.
It is a development/demo surface, not a production operator plane. Authentication is a development mode, several routes are auth-gapped or config-gapped depending on the deployment, and browser keyboard/focus behaviour was not re-driven in the review pass.
Lifecycle position
Where it sits in the governance lifecycle
Stage numbering is canonical across the site. Open the interactive lifecycle to see every component with responsibilities at each stage.
Decision
Coordinate policy, constraints and uncertainty.
Evidence and audit
Keep linked, ordered, reviewable records.
Verified capabilities
What is verified today
Capabilities are drawn from the product register. Each one is bounded by the limitations stated further down this page.
- Same-origin backend-for-frontend with no open proxy
- Permission-checked read routes over platform services
- Operational read models for governance, evidence and network surfaces
- Development authentication mode for local evaluation
Outputs
- Operational read views
- Proxied read models
- Findings and status surfaces
Evidence and maturity
What the evidence supports
Maturity describes verified engineering evidence in a bounded environment. It is not a production-readiness statement.
Maturity note
Same-origin BFF read paths were verified at the HTTP boundary in the live RC audit: real backend data, permissions enforced, no open proxy and no token leak. The console runs in development authentication mode and browser interaction was not re-driven.
Not production-qualified
This label describes verified engineering evidence only. No production deployment, certification, benchmark or customer outcome is claimed.
Evidence recorded
- Capability audit 2026-11-03: 60 console-facing capabilities classified; 26 verified read capabilities.
- Acceptance step 15: real backend data through the proxy, permissions enforced, no token leak.
- Platform API audit: development authentication posture disclosed.
Dependencies
- Control Plane
- Gatekeeper
- AIOps
- audit ledger
Dependencies are stated as the product register records them. A dependency is not automatically production-qualified; see its own product or component page for its maturity and limitations.
Limitations
What this product does not do (yet).
Limitations are stated before the evaluation questions so they cannot be missed, downplayed or treated as future-work footnotes.
Limitations — read before evaluating
- Development/demo surface with local development authentication; not a production operator plane.
- Browser rendering, keyboard and focus behaviour were not re-driven in the review pass.
- Some routes are auth-gapped or config-gapped depending on the deployment.
- No multi-tenant SaaS console, SSO or MFA is claimed.
No capability on this page should be read as production qualification. If a limitation is material to your use case, it belongs in the evaluation scope — not after it.
Relationship to the platform
How it fits
The Console is an operator read surface over the Control Plane, Gatekeeper, AIOps and evidence services. It has no admission or dispatch authority: the backend authorises, and the console can only display or request what its permissions allow.
Evaluation questions
- Which read surfaces do operators actually need first?
- How is the console's identity configured for a real deployment?
- Can a reviewer distinguish a displayed state from a verified backend state?
Next step
Evaluate NiGeNje Console against a real control problem.
Bring a system boundary, an action class and a failure mode. The first step is to agree what should be governed and what evidence would count.