blackroad-os/blackroad-os-docs
9
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: migrate docs to docusaurus v3 hub

Browse Source
This commit is contained in:
Alexa Amundson
2025-11-24 04:33:44 -06:00
parent 21637b1e6f
commit 2979029c38
105 changed files with 5676 additions and 198 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
versioned_docs/version-v0.1/packs/finance/pain-points.mdx Normal file
View File

@@ -0,0 +1,24 @@
---
id: finance-pain-points
title: Pain Points Summary
slug: /packs/finance/pain-points
sidebar_position: 2
---
BlackRoad OS targets the friction that comes from fragmented tooling, unverifiable automation, and opaque ROI. Use these talking points when aligning stakeholders or writing proposals.
## Too many siloed dashboards
- **Problem** — Operators juggle consoles for infra, agents, finance, and compliance with no shared view.
- **BlackRoad OS response** — Prism Console aggregates operational health, finance signals, and events; API provides one consumable surface for custom views.
## No unified audit trail across agents and infra
- **Problem** — Actions taken by agents or scripts lack provenance and are hard to defend during audits.
- **BlackRoad OS response** — DomainEvents and RoadChain provide a tamper-evident journal, anchored by PS-SHA∞ identities, and visible in Prism.
## Difficulty quantifying automation/AI ROI
- **Problem** — Automation is measured by anecdotes instead of accountable metrics.
- **BlackRoad OS response** — Finance snapshots in Prism tie agent actions to costs and returns; events create traceable evidence for each outcome.
## Manual ops & fragmented infrastructure
- **Problem** — Deployments, DNS changes, and incident response require manual steps scattered across runbooks.
- **BlackRoad OS response** — Operator-hosted agents (Atlas, infra bots) plus `blackroad-os-infra` blueprints centralize the path from request to action, with clear environments and rollbacks.