Opening reviewed archive snapshot…
Opening reviewed archive snapshot…
Engineering archive / CP-AFRICAN-BUSINESS-NETWORK
A reviewed view of the executable monorepo foundation, Identity and Organization core, permissions package and documented enterprise boundaries.
Claim / Public evidence / Source / Limitation
Reviewed public claims with explicit confidence and proof boundaries.
The public tree contains apps/web, apps/api, packages, services, infra and docs.
Inspect evidence +The repository makes platform boundaries inspectable.
The public tree contains apps/web, apps/api, packages, services, infra and docs.
The presence of directories does not prove that every represented subsystem is implemented.
Several broader business modules contain placeholders and are explicitly out of the current scope.
Public TypeScript types expose organization-scoped users, memberships, statuses and the three implemented MVP roles.
Inspect evidence +The domain vocabulary exists in executable, strongly typed code.
Public TypeScript types expose organization-scoped users, memberships, statuses and the three implemented MVP roles.
Type definitions do not prove complete domain invariants or persistence behaviour.
The implementation currently represents a deliberately small identity and organization core.
The implementation maps minimum roles per action and returns explicit allow or insufficient-role decisions.
Inspect evidence +The lab can reproduce an actual public policy decision without calling the application.
The implementation maps minimum roles per action and returns explicit allow or insufficient-role decisions.
This small role policy does not prove the broader documented RBAC, ABAC and PBAC matrix is implemented.
The code currently exposes only Owner, Admin and Viewer and four generic actions.
The API tree contains implemented organization, memberships, auth, users, outbox, audit and platform areas, while broader business modules remain placeholders.
Inspect evidence +The portfolio can distinguish executable foundation from documented future scope.
The API tree contains implemented organization, memberships, auth, users, outbox, audit and platform areas, while broader business modules remain placeholders.
This does not prove that invoices, payments, inventory, documents, automation or production AI workflows exist.
The public README explicitly lists those broader modules as outside the current scope.
ADR 0002 documents strong domain boundaries, internal events and an outbox pattern as the intended MVP direction.
Inspect evidence +The decision avoids premature distributed-systems overhead while preserving extraction boundaries.
ADR 0002 documents strong domain boundaries, internal events and an outbox pattern as the intended MVP direction.
An accepted ADR does not prove that every stated boundary and pattern is implemented.
This evidence is architectural documentation, not runtime validation.