Platform

The core in detail.

supakraft connects brand truth, task facts, rules, checks, approvals and delivery in one versioned run. Further knowledge domains keep their own authority and are connected through clearly separated resolvers.

01What the core governs

Four parts carry a run between them.

Brand Core
The authoritative source for brand truth: approved, scoped, with source, validity and knowledge state. The rest of the business information does not sit in it.
Control Layer
The control layer binds the run to rules, versions, checks and approvals. A missing required check is not treated as passed. It is not a general scripting system.
Run Contract
Task facts, actor and execution policy describe the concrete operation: what is asked, who acts and what is permitted.
Access and surfaces
UI, API, MCP and partner tools call the same core operations. Enforcement stays in the core.
02Six stages

The order is part of the architecture. Generation is not approval, and approval is not delivery.

  1. 01Resolve

    Exact identities, authority, scope, validity and conflicts.

  2. 02Compile

    Compose already resolved inputs into a pinned task context package. The package is model neutral.

  3. 03Execute

    Bind package, policy and renderer before the provider call.

  4. 04Verify

    Check the stored output against its acceptance contract.

  5. 05Approve

    A verified eligible person approves the exact stored subject.

  6. 06Deliver

    Recheck current eligibility before the external effect.

03Knowledge domains and run contract

Four knowledge domains with their own authority, and beside them the contract that describes a single run.

Knowledge Domains

Brand Core
Governed brand truth under OBDS contracts.
Proven in the shared core
Product and Service Knowledge
Product and service facts from PIM, ERP or catalogue.
Next bounded expansion
Dossier
Business context, non-authoritative by default.
Integration not yet established
Asset Knowledge
Identity, rights, validity and descriptive metadata of assets.
Integration not yet established

Run Contract

Task Facts
What this run asks for, resolved before execution.
Actor
Who acts, with what eligibility.
Execution Policy
What is permitted in this run and what stops it.

Task facts are not a fifth knowledge store. They describe the concrete operation.

04Authority and retrieval

Retrieval finds candidates. Retrieval does not grant authority.

Architecture example, next bounded product proof
PIM:                    8 hours
old product document:  10 hours

Retrieval may find both. The product authority decides which value is admissible as a factual basis. The conflict remains evidence.

This product path is described, not proven. It is the next bounded expansion of the shared core.

05Status

What is proven today.

The shared core has proven a deliberately narrow governance path for brand truth. The proof covers defined core commands, a versioned execution basis, bounded checks, human approval, withdrawal and deterministic delivery within the tested boundaries.

Next

Product and service knowledge is being integrated as the first additional knowledge domain and falsified against contradictory sources.

Not yet claimed as a general capability

  • Broad marketing generation
  • Dossier integration
  • Asset knowledge integration
  • Generic external delivery
  • Equivalence of UI and MCP
  • Whole-product OBDS conformance

This list is maintained as development proceeds.

06Surfaces and adapters

Apps, forms, agents, PIM and DAM connectors and partner tools live above the core. They may vary by deployment. Enforcement stays in the core.

Surfaces

UI, API and MCP call the same governed operations. Full equivalence between these routes is not yet established.

Adapters

An adapter translates between an external system and a domain. It does not decide what is true.

Agents

Agents can be added as surfaces when their operation is covered by a core contract. Delegated access does not turn a machine into a human approver.

07Boundary to the open standard

OBDS defines governed brand truth. supakraft uses those contracts inside a wider operating core. Product facts, dossier context, asset rights, actor identity, execution policy, approval and delivery are separate supakraft concerns. They do not become brand truth merely because they participate in the same run.

What the standard means