General enquiries
Email, no published SLA
Use the public mailbox for questions or to request managed access. The reference docs and static service-information pages are available without an account.
Support & help
Help, when the loop matters.
BearScope is the live product today, and the generalized Fibric platform is available through managed early access. Start with the reference material below, check the published service information, or write to the support mailbox for help with an active engagement.
Start here
Most answers are already written down.
The docs cover the envelope, how the AI proposes and a deterministic check disposes, connectors, and governance. If something is unclear, that's on us. Tell us and we'll fix the page.
Read
Documentation
Core concepts, connectors, governance, and proposed SDK and API surfaces. These pages describe the reference contract; they are not a public developer service.
Read the reference docs → BuildQuickstart
Walk through the proposed setup and governed execution model. The public quickstart is a reference preview, not a runnable self-service flow.
Read the quickstart preview → CheckSystem status
A plain-language statement of what is live, what is in managed early access, and whether public uptime monitoring is available.
View service information →
Talk to a human
No bots on this end.
If the reference material does not cover it, write to us. The mailbox is the public route for support and managed-access questions; response commitments apply only when they are part of your engagement.
A good report gives us a better chance of correlating what happened. If your supported workflow exposes an action ID or idempotency key, include it along with the time and connector involved.
- What to include
- 01Your tenant. The workspace or account name, so we look at the right walled-off data and nobody else's.
- 02What you expected, and what happened. One sentence each beats a paragraph of context.
- 03The available action ID. If that workflow exposes one, include it so we can correlate the supported execution record.
- 04When it happened. A rough timestamp and your timezone. It narrows the search fast.
- 05Connector and capability. Which system was involved, so we know which connector behind the capability to check.
Support arrangements
Scoped to the service you run.
The public site does not publish a universal support SLA or live monitoring feed. Response routes and availability commitments are confirmed for each managed engagement. See availability for the current implementation boundary.
Customer support
Route set by engagement
BearScope customers use the support path and response targets established for their deployment. Those terms are not inferred from an indicative website plan.
Deployment support
Defined during scope
Connector ownership, escalation routes, response targets, and any availability commitment are agreed before a managed pilot or production deployment begins.
Nothing on this page creates a contractual response or availability commitment. Those terms, when applicable, are stated in the relevant customer agreement.
Security & disclosure
Found something? Tell us safely.
Supported governed-action paths are designed to fail closed when required policy checks cannot complete. Found a vulnerability? Use the disclosure route so the report reaches the right team without first publishing sensitive details.
Trust & security
The current BearScope boundary, tenant isolation, supported execution records, policy checks, and the limits of compensation and recovery.
Read the trust page →Responsible disclosure
How to report a security issue, what we ask of you while we investigate, and what you can expect from us in return. Please don't post issues publicly first.
Disclosure policy →
Questions
The things people ask first.
Short, honest answers. If yours isn't here, the docs go deeper, and support@fibric.io goes deeper still.
BearScope is live for governed CX operations. The generalized Fibric platform, public CLI, API, and SDK are not available as self-service products today. Use managed access to describe the deployment you want evaluated.
There is no public checkout or generally available free platform tier today. The figures on pricing are indicative planning assumptions for managed early access; actual commercial terms are confirmed in a scoped quote.
In the current live BearScope implementation, governed rows use tenant-scoped controls and the UI marks fallback data so it does not present as a real metric. Supported action paths can produce attributable records. Recovery depends on the downstream connector and is not a promise that every action can be reversed. See the trust page for the boundary.
There is no universal public SLA or live monitoring feed. The status and availability pages are static service information. Any response or availability commitment is scoped contractually for the relevant managed deployment.
Capability-to-connector indirection is intended to make substitution possible, but a swap still requires connector implementation, authorization, data mapping, policy review, and parity testing. The connector reference describes the target contract; support can help scope a migration.
Managed access
Scope the system, controls, and support path.
Tell us what you run and what outcome you want evaluated. We will confirm maturity, connector coverage, safeguards, and commercial terms before any managed deployment.