FENiOS
FENiOS is the work-in-progress operating layer for Fenrua’s public protocol system. It is designed to coordinate project requirements, FEN token-state language, Chain 978 support context, Chain 521 research context, FENDEF public policy, FENtrust evidence, and council signal interpretation without exposing protected execution infrastructure.
The technical ambition is an OS-shaped review surface: a serious AI project should be able to describe what it needs, receive chain-aware protocol context, see the evidence boundaries attached to that context, and leave with reviewable language rather than generic marketing copy.
The richer version is a context pack, not a monologue: which FEN surface applies, which chain lane is relevant, which token state is being discussed, which public evidence can be cited, what private controls remain out of scope, and what the builder can safely review next.
FENiOS live review surface
Public FENiOS output is review context, not privileged execution. The interface may assemble project, protocol, chain, and evidence context, but it does not approve protected actions.
Abstract 1. Section Abstract
This section treats FENiOS as a coordination system for a protocol with many distinct states. Its purpose is to keep AI project requirements, FENswap quote state, P-FEN receipt state, claimed FEN state, Chain 978 support context, Chain 521 research context, FENDEF policy, FENtrust evidence, and FENcouncil signals from collapsing into generic assistant prose.
OS method: intake must resolve to state, evidence, boundary, and review output before it can become public protocol language.
Research Question 1. RQ-OS-01
It must map user/project context into token state, chain state, evidence state, review state, and protected-execution boundaries.
Research Question 2. RQ-OS-02
The output should identify project fit, relevant FEN pillar, evidence requirement, boundary condition, and next review step.
Research Question 3. RQ-OS-03
It must refuse private signing, privileged execution, protected route disclosure, validator operation, reserve action, and bypass of human/operator review.
| Claim | Statement | Evidence | Boundary |
|---|---|---|---|
| Formal Claim 1. FC-OS-01 | FENiOS is a coordination layer over the ten FEN pillars. | The orchestration diagram maps project intake through FEN lanes, 978/521 chain context, FENtrust evidence, review artifacts, and protected boundary. | The public interface does not become a privileged execution system. |
| Formal Claim 2. FC-OS-02 | FENiOS output is admissible only when it preserves state separation. | OS metrics require chain context, evidence mode, coordination scope, and protected execution mode. | An answer that collapses P-FEN, claimed FEN, Chain 978, Chain 521, or FENDEF into one generic claim is inadmissible. |
| Formal Claim 3. FC-OS-03 | The chat panel is a review surface, not a control panel. | The section frames the live interface beneath operating principles and public-boundary language. | The panel cannot approve privileged actions or expose private infrastructure. |
Invariant 1. INV-OS-01
The flow requires intake, protocol-state resolver, chain-aware routing, evidence assembly, and review artifact generation.
Invariant 2. INV-OS-02
Chain 978 and Chain 521 are explicitly represented as separate context fields.
Invariant 3. INV-OS-03
The final flow node and boundary cards exclude private controls, privileged procedures, and operator-only mechanics.
| Row | Artifact | Observation | Limitation |
|---|---|---|---|
| Evidence Row 1. OS-01 | lib/nexus/fenios-router.ts | Defines routing concepts for FENiOS behavior in the application layer. | Router implementation does not mean public chat may perform privileged writes. |
| Evidence Row 2. OS-02 | lib/nexus/fenios-openai.ts | Connects FENiOS interaction logic to a model-backed review surface. | Model output remains advisory and must respect source-backed boundaries. |
| Evidence Row 3. OS-03 | app/api/nexus/fenios/route.ts | Provides the API boundary for the public FENiOS panel. | An API route is not a proof of privileged access or operational approval. |
FENiOS orchestration diagram
FENiOS is presented as a coordination layer because Fenrua has multiple states that must stay separate: quote state, receipt state, claim state, support-chain state, research-chain state, economic-policy state, and public trust state.
coordination scope
10 pillars
Every response should map back to the FEN public architecture.
chain context
978 / 521
Support-chain and research-chain contexts remain separated.
evidence mode
source-backed
Trust claims should point to records, snippets, hashes, or live progress.
execution mode
protected
Public chat does not open privileged write paths.
The OS surface can prepare review language and explain protocol fit, but it must not expose private write paths, protected integration mechanics, or operator-only procedures.
FENiOS is not a generic chatbot wrapper; it is the public coordination language for a protocol that has receipt state, claimed-token state, chain state, research state, economic-flow state, and public evidence state.
The OS layer should turn a messy project request into a clean context pack: protocol fit, applicable lane, token state, evidence requirement, risk boundary, and next review step.
A public answer is only useful when it keeps protected execution out of scope. The UI can assemble context, explain boundaries, and prepare review language, but it must not turn private operations into browser-accessible controls.
The public FENiOS surface can explain, classify, draft, and assemble review context.
It cannot approve privileged actions, expose signing paths, publish private infrastructure, or bypass human/operator review.
Outputs should stay attached to the 10 FEN pillars and cite FENtrust-style evidence when making protocol claims.
Low-fee AI hosting, support-chain settlement, and token-state grammar.
Contract source records, PFENPresale snippets, report hashes, and public statements.
Low-fee hosting context, builder support, settlement language, work records, and public continuity.
N/P-521 evidence, circuit receipts, gas observations, research contract posture, and release boundaries.