The problem
Anyone operating Senior X knows the cycle: a business area asks for a new view of its data, the request becomes a ticket, the ticket becomes a meeting, the meeting becomes a prototype — and weeks later the screen arrives different from what was asked. The information exists; the path to it gets lost between conversation, querying and approval.
Who it serves
Senior X customers who want to see a solution before publishing it, keeping control and traceability. Channels and consultancies that want to amplify the consultant — Braga Suite does not replace the channel: discovery, decisions, approval and the tenant relationship stay human.
The proposal
Braga Suite organizes the journey that is normally scattered. Agent v2 works with tenant-allowed capabilities, records evidence for every data-backed answer, turns the need into a reviewable screen (ScreenSpecV1) and requires approval from a second role before publishing.
The flow
- Business need
- Query through an allowed capability
- Recorded evidence
- Screen artifact (ScreenSpecV1)
- Preview and refinement
- Publish request
- Human approval by another role
- Simulated publishing → screen route
Architecture and data boundaries
The browser never sees secrets: every integration (including senior-mcp, the specialized knowledge layer) lives in the BFF, server-side. Conversations are segregated by tenant and user; the orchestrator caps tools per call and demands evidence on data-backed answers; a redaction-check sweeps the whole repository for credential and identifier leaks.
Governance
Three roles — viewer, creator and publisher. Whoever creates a screen cannot approve it: self-approval is blocked by construction, not by convention. Every revision has a diff and history; publishing requires a second human.
What works today
- Conversations segregated by tenant and user
- Capability catalog per tenant
- Evidence required on data-backed answers
- Screen creation, preview, refinement and diff (ScreenSpecV1)
- Approval by a distinct role, self-approval blocked
- Governed simulated publishing, with a local screen route
Under controlled validation
- Real screen publishing to Senior X
- Live senior-mcp querying (authorized smoke test)
- Real, authorized Senior X customer session
Future vision
- Multi-company commercial SaaS
- BYOK — customer brings their own model key
- Per-tenant quotas and billing
Engineering evidence
Numbers from the local assessment of July 11, 2026 — they prove engineering consistency, not production operation.
My role
Concept, integration architecture, BFF, agent orchestration, design system and workbench UX. An independent product, built for the Senior X context.
Braga Suite is an independent solution. Third-party brands and product names belong to their respective owners.