PlausibleBA is not a prompt wrapper. It encodes BIZBOK-grounded methodology so BAs get structurally correct outputs without needing to know the framework.
The Business Architecture Guild's BIZBOK (Business Architecture Body of Knowledge) is the reference framework for the PlausibleBA skills. Our capability maps, value streams, and business concepts are three of the core metamodel elements of classic business architecture.
PlausibleBA is not intended as a substitute for Business Architecture. We advocate that any artefact created from PlausibleBA foundation content should be aligned and integrated into a comprehensive business architecture model, by a business architect. Our intent is that doing so should not slow you down. Business Analysts operate under intense time pressures of project deadlines and can't afford to get bogged down in arguing over abstractions. Their skills are in elicitation workshops, requirements engineering and analysis techniques. A "just enough, plausible model" is intended to assist in those tasks. Alignment with the model of record is the domain of the business architect.
The distinction matters. PlausibleBA's goal is to enlist Business Analysts to promote business architecture on their projects, producing artefacts that are structurally sound and compatible with architecture principles. At the end of the project, BA's leave behind an enduring asset for their business stakeholders, to be curated by business architects.
What the business is able to do — independent of how it's organised or what technology it uses. Stable over time.
How the business delivers value to a recipient through a sequence of stages — orchestrating capabilities into a coherent flow.
The things the business manages, exchanges, and records — the nouns that ground the capabilities and flow through the value stream.
PlausibleBA classifies all business objects using the Capsicum Triad — Party, Record, Resource. The triad is grounded in REA theory (McCarthy 1982) and Mario Bunge's ontology of social systems.
REA (Resources, Events, Agents) provides the economic foundation: every business exchange involves a resource being transferred between agents, with records documenting the event. The Capsicum Triad maps directly onto this: Resources are the things of value, Parties are the agents, and Records are the evidence.
The triad is deliberately minimal — three types is enough to classify every business object in any domain. More types introduce ambiguity. Fewer types lose discriminating power.
A person or organisation that plays a role in the business.
Owner · Guest · Contractor · Tenant
A thing of value that is managed, exchanged, or consumed.
Property · Portfolio · Booking · Tenancy
A document that captures evidence of something that happened.
Financial Report · Guest Review · Maintenance Request
Every PlausibleBA skill exports a ba-skills-bundle.json — a schema-validated JSON document that imports directly into the Value Cognition Canvas (VCC).
VCC is a business architecture workshopping platform built by the same team. It takes the structural scaffold produced by PlausibleBA and adds analytical layers: friction heatmaps, solution mapping, throughput projections, governance controls, and facilitated stakeholder workshops.
PlausibleBA is the front door to VCC. The skills produce the structure — free, in any Cowork session. VCC adds the analysis — for teams who need to go deeper.
The name PlausibleBA is intentionally ambiguous. To the IIBA crowd it reads as Business Analyst. To the Guild crowd it reads as Business Architecture. Both readings are correct.
The mission is to enlist Business Analysts — who are already doing analysis, requirements, and process work on every project — to produce business architecture artefacts as a natural extension of their existing practice. Not a separate discipline. Not a separate role. Just enough biz arch, done at project scope, using tools they already have.
A BA who runs /capability-map on their project isn't doing "business architecture". They're doing their job better — with a structured, validated, cross-referenced output that any enterprise architect can read, any stakeholder can validate, and any VCC session can extend.