After Framework

Glossary

Consistent definitions for the technical terms used across the docs.

Docs version: supercore main · packages 1.0.0
Shared kernelLink to this section: Shared kernel
after_core: the base package every product depends on. It defines ports and default implementations.
PortLink to this section: Port
An interface defined by the platform, such as AfterAuthRepository. Feature code depends on ports, never on vendor SDKs.
AdapterLink to this section: Adapter
A concrete implementation of a port, for example Firebase auth, bound at the composition root.
Composition rootLink to this section: Composition root
The single place where a product wires its manifest, standard overrides and adapters, usually lib/app/platform/after_framework.dart.
Provider overrideLink to this section: Provider override
A Riverpod override that replaces a default platform provider with a product adapter.
ManifestLink to this section: Manifest
AppPlatformManifest: the product's identity — app name, appId, package names and product line.
Product lineLink to this section: Product line
consumer or enterprise. It decides whether a product layers after_consumer or after_enterprise on the kernel.
Life DomainLink to this section: Life Domain
A consumer area of life that one product owns, such as mobility for SuperGarage.
Industry DomainLink to this section: Industry Domain
An enterprise vertical that one product owns, such as hospital operations for SuperHospital.
Ecosystem fabricLink to this section: Ecosystem fabric
after_ecosystem: shared identity, subscription, events and cross-product APIs.
Product specLink to this section: Product spec
product.spec.yaml: the small file the factory turns into a product. It contains only product-owned concerns.
Fail-closedLink to this section: Fail-closed
When required context is missing, the operation throws instead of returning broader data.
Scaffold modeLink to this section: Scaffold mode
AfterBootstrapMode.scaffold: mocks and in-memory adapters are allowed. Production mode rejects them at startup.
BYOKLink to this section: BYOK
Bring your own key: AI provider keys are stored in the credential vault on the device, never shipped in the client.