Documentation baseline
This revision describes the upstream default branches checked on 5 November 2026. It documents source behavior; it does not announce a stable release or imply that every package mirror already contains these changes.
| Source | Branch | Revision |
|---|---|---|
| OpenAF | master |
06414cd9 |
| oJob-common | master |
130addf4 |
| oafp | main |
35a922f9 |
| openaf-opacks | master |
87b07e97 |
Check the runtime and processor you actually use:
oaf -c 'print(getVersion()); print(getDistribution());'
oafp -v
oafp help=usage
opack list
The OpenAF distribution bundles an oafp implementation. The oafp development repository and the oafproc oPack have separate update histories. The usage, filters, templates, examples, and JSON Schema guide follow the pinned oafp development source. Check installed help before using a newly documented option. The core processor overview follows the OpenAF source snapshot.
Changes covered by this revision
- Graph channels and time-series channels: persistence, backing channels, retention, traversal, metrics and queries.
- Desktop windows and terminal views, the optional JavaFX provider, and the screen reference.
- LLM decisions, provider APIs, schema output, and MCP authentication.
- JDBC execution policy, Jakarta XML Binding migration, CLI and console improvements, and Markdown-aware ODoc.
- oJob-common modules, including HTTP/REST metrics, file-browsing restrictions, MCP authorization, file operations and watchdog behavior.
- The corrected oafp query pipeline, streaming semantics, DSV, Base64, HTTP input/output, map comparison, charts and shell completion.
- The complete oPack catalog, with focused guides for Lambda/MicroVM, gRPC, AWS, AI providers, observability, data integrations and desktop tools.
The October snapshot remains available as historical context. Follow current topic guides for current contracts.
How to interpret examples
Guides identify required libraries, external services and credentials where relevant. Commands that deploy resources, modify databases or manage system services require a suitable test environment and deliberate configuration. Source review and local fixture tests do not establish provider account access, production readiness, GUI behavior or support on every operating system.
Examples involving nAttrMon, the remote ojob.io catalog or other repositories retain their own upstream requirements. Their external implementations are outside these four source snapshots.
The repository’s contributor README explains how to reproduce imports, reference generation, link checks and the site build. Source mappings and review evidence are maintained under utils/.
Source discrepancies handled here
Some upstream prose describes APIs that are absent or behave differently in the implementation. The core overview, Sigil guide and validation guides contain reviewed corrections. The MCP guide distinguishes HTTP and STDIO result conversion. These are documentation corrections; the upstream runtimes have not been changed by this site revision.
The pinned standalone oafp build references a missing src/include/inputLineFns.js. Its development-source documentation is included, but the local processor smoke tests use the processor bundled in the pinned OpenAF build. Cloud, native GUI and external-service examples remain dependent on their own environments.