| layout | home | |||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| hero |
|
|||||||||||||||||||||||||||||||||||
| features |
|
OpenFoundry now organizes its official documentation around these top-level capability areas:
- AI Platform (AIP)
- Data connectivity & integration
- Model connectivity & development
- Ontology building
- Developer toolchain
- Use case development
- Observability
- Analytics
- Product delivery
- Security & governance
- Management & enablement
This documentation still stays grounded in the repository itself:
- how platform capabilities map onto
services/*,libs/*,apps/web,proto/*, andinfra/* - how contributors build, test, and ship changes
- how ontology-centric workflows fit into the current OpenFoundry architecture
- how docs, contracts, SDKs, and deployment assets are delivered
- Getting started for contributor orientation.
- Ontology building for the core platform semantics.
- Architecture center for runtime and contract boundaries.
- Platform updates for release-facing changes in the docs set.