These docs describe the target Fibric platform contract and proposed developer experience. Public Fibric CLI, API endpoints, and SDK packages are not yet available. All present-tense API, CLI, SDK, tenancy, security, retention, retry, and pricing language below is normative target language, not a statement that the surface is callable or commercially available today. Commands, package names, URLs, responses, limits, and timelines are reference examples unless a page explicitly identifies a deployed BearScope path.
Roadmap & release notes
Fibric has not announced a stable public developer-platform release. This page separates what is verifiably available from the interfaces documented as targets, and states the evidence required before those targets become public releases.
A feature belongs in release notes only when a user can reach the named surface, follow a maintained setup path, and verify the documented behavior. A source-level reference implementation, design contract, or illustrated command is not a public release.
The Fibric architecture exists as a product contract and reference implementation. BearScope is the live product surface; the generalized developer platform described across these docs remains a reference preview.
- BearScope, a tenant-aware CX operations product with governed real-data paths for its live tenant.
- A source-level Fibric kernel and connector contract used to define the intended envelope, plan, policy, execution, and receipt boundaries.
- This documentation preview and a marketplace catalog whose individual listings carry their own availability state.
- The
@fibric/cli,@fibric/sdk, and@fibric/connector-sdkpackages described in examples. - A general-purpose
api.fibric.ioendpoint, public sandbox, developer workspace, or self-service API-key flow. - A stable semver line or compatibility promise for the proposed CLI, APIs, SDKs, connectors, and operator runtime.
The next credible release milestone is a managed preview with a deliberately narrow support boundary, not an implied self-service platform.
- A reachable preview environment with a documented owner, support path, tenant-isolation test, and availability scope.
- An installable package or maintained source-install path whose quickstart runs from a clean machine.
- Working authentication, key rotation, idempotency, receipt retrieval, and connector failure tests against the preview environment.
- Reference pages labeled by maturity: live in BearScope, managed preview, reference contract, or planned.
A stable version will be named only after the public artifacts and hosted behavior exist and compatibility is covered by repeatable tests.
- Published artifacts, signed release provenance, supported upgrade paths, and a public compatibility policy.
- End-to-end contract tests for tenancy, fail-closed policy evaluation, duplicate suppression, connector retries, and receipt integrity.
- Operational status and incident communication tied to monitored services rather than a static status claim.
- Release notes generated from shipped artifacts and verified deployment evidence.