Developer Start Here

Purpose

The Developer lane explains how to build and maintain Amvionlie without creating drift.

This lane is for implementation work: addon contracts, ownership boundaries, central helpers, route contracts, public targets, frontend access, install/update behavior, and verification. User operating instructions belong in the Users Guide. Internal process rules stay internal.

Build from ownership first

Before adding code, identify the owner:

• Core owns runtime rails, security helpers, route dispatch, identity helpers, list controls, and shared primitives.
• Admin owns the admin shell and admin navigation surface.
• Each addon owns its own schema, permissions, routes, runtime, admin behavior, and public behavior.
• Menu Manager owns public navigation.
• Widgets owns widget definitions, placement, visibility, assignments, and Dashboard handoff.
• Dashboard displays assigned widgets; it does not manage widget definitions.
• Permissions owns roles, groups, permission keys, frontend access evaluation, and access boundaries.

If you cannot name the owner, pause. The system is already telling you the work is not ready for code yet.

Build path

Follow this sequence when building a governed addon:

1. Build Your First Addon
2. Governed Addon Checklist
3. Manifest Contract
4. Install Contract
5. Schema Contract
6. Permissions Contract Basics
7. Admin Routes
8. Public Routes
9. Frontend Access and RBAC
10. Public Targets and Menu Placement
11. Verification and Smoke Tests
12. Changelog Entry Rules

Reference path

Use Current Addon Contract Shape and the Reference Samples space when you need copyable file shapes. Samples are reference material, not a substitute for understanding ownership.

Golden rule

Do not copy the easiest old pattern. Copy the current governed pattern. If two patterns disagree, the newer governed owner wins.