What BSP is
Every business system carries its own model of the same transaction. An order in a storefront and the same order in an ERP are named, structured and statused differently, and a single status token often compresses several independent facts: has it been paid, has it shipped, is it still wanted. Humans absorb that ambiguity. Software integrations paper over it with point-to-point field mapping. Autonomous agents cannot: an agent that acts on business state needs a definition of that state that does not depend on which vendor happened to store it.
The Business State Protocol is a specification for:
- expressing what a system asserts about a business object, as evidenced claims rather than bare values;
- establishing that two systems’ records describe the same real-world object;
- determining whether their views of it are congruent, conflicting, stale, or unknowable.
It is not another universal order schema, not an event transport, and not an agent communication protocol. It is designed to sit above existing standards for those things and to be carried by them.
Status
Section titled “Status”Version 0.1 is in preparation. See Status.