Role-Based Paths

Documentation status: guide — see Maturity and evidence.

This section routes readers to canonical documentation according to their responsibilities. Role pages do not replace the API or architecture guides.

Choose a role — direct entry

• Application Developer — models, actions, views and SDKs.
• FPL Developer — functionalP/FPL execution.
• Architect — boundaries and deployment topology.
• Platform Integrator — runtime, ABI and operations.
• Core Developer — source-level contracts and tests.
• CIO — architecture and governance.
• Head of R&D — evidence and industrialization.

Browse by task · Native Runtime

Main paths

• Application Developer — models, actions, views, services, and SDKs;
• FPL Developer — scripting and functional logic;
• Architect — boundaries, topologies, contracts, security, and evolution;
• Platform Integrator — Runtime, service, data, and deployment integration;
• Core Developer / Maintainer — internals and validation;
• CIO / Head of R&D — governance, adoption, and technical trajectory.

Rule

A role page explains what to read and which decisions to make. For an exact signature, syntax, or contract, return to API, Architecture, DevOps, or Bindings.