00Operating Core

AI made your marketing faster.
It did not make it better.

supakraft is the operating core for AI marketing operations. The core binds a task to the brand truth, the scope and the rules that apply to it. If a precondition is missing, the run stops. Verification, human approval and delivery stay separate steps.

Book a demoSee the platform

30 minutes on the system, along a single run.

  • Open standard for brand truth
  • Isolated instance per client
  • Traceable runs with human approval
  • Built in Vienna
01The problem

Rules nobody applies govern nothing.

Four things that sit side by side in most organisations without being connected.

01

Guidelines are passive documents

Two hundred pages on the intranet, a PDF in the DAM, a deck from the last rebrand. A document can describe what applies. It cannot apply itself.

02

Generative tools do not know which source ranks

A model finds material. Which source is authoritative for this specific task is not stated in the material itself. So it gets guessed.

03

Review becomes the control layer by accident

Because nothing decides beforehand, review decides everything. One person checks, feedback takes days, and under deadline pressure the step disappears.

04

Product data, assets, brand truth and task context live in separate systems

PIM, DAM, guidelines and brief. Before every output somebody would have to bring them together and settle the contradictions. Mostly that does not happen.

02What supakraft is

The core sits underneath the tools.

supakraft does not produce content in place of your tools. The operating core records which information may apply to a task, on what basis a model was called, which checks ran and which person approved.

Models, surfaces and connectors can change. The governance boundaries stay the same.

Generation and governance are different layers

Generative tool

  • Produces or edits content
  • Brings its own interface and its own model behaviour

Governed core

  • Resolves which authority applies to the task
  • Binds evidence and policy to the run
  • Records checks and approval

Surfaces come after the core

Apps, forms, agents and partner tools call governed core operations. A surface may differ by client. The enforcement behind it must not.

See the platform
03How the core works

One run, six stages.

A governed run follows the same sequence, from task to delivery. What cannot be resolved in one stage is not guessed in the next.

  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.

Information sources keep their authority

An adapter translates. It does not decide what is true.

Which domain is connected in a given deployment is stated on the platform page.

Brand Core
Governed brand truth: approved, scoped, with source and knowledge state.
Product and service
Facts from PIM, ERP or catalogue, with their own source and their own authority.
Dossier
Business context, non-authoritative by default.
Assets
Identity, rights, validity and descriptive metadata.
Task facts
The concrete run request, resolved before execution.
04Authority

What counts as brand truth.

Brand truth is held as approved, scoped information. An element carries source, validity and knowledge state. A rule can require or forbid something. Missing truth is not filled in from model knowledge.

Four knowledge states

defined
A value is decided and approved.
unknown
A value is expected and open. It stays open.
not_defined
The brand deliberately defines no value here.
not_applicable
The value does not apply in this scope.

For people and for systems

Brandbooks remain useful for people. The brand core additionally holds the approved decisions in a form software can resolve and check. Both can reference the same sources, but they are not the same object.

For people

  • Colour value with source and approval state
  • Rule in plain language, with an example and a counter-example
  • Claim with validity and expiry

For systems

element: colour.primary
value:   "#1F2AFF"
state:   defined
source:  brandbook, section 2.1
scope:   [ web, print ]

element: colour.secondary
state:   unknown
note:    no value decided, not derived

Schematic, in the format of the open standard. No real client data.

The boundary of the brand core

  • The brand core is the authoritative source for brand truth.
  • Product data, dossier context and assets keep their own sources and their own authority.
  • An approved output stays an approved output. It does not rewrite brand truth automatically.
  • Changes to brand truth are separate, authorised decisions.

Every governed run preserves the basis used for the decision. A reviewer can see which release, rules and evidence were used.

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.

06Open standard

Brand truth sits in an open format.

The Open Brand Definition Specification is published by Kill The Dragon GmbH and is separate from supakraft. The brand core uses its contracts. Specification under CC BY 4.0, implementation layer under Apache 2.0.

01

No vendor format

Brand truth is described in an open, documented format. supakraft can store that data operationally, but the format itself is not proprietary.

02

Independently implementable

The format is machine-readable and independently implementable. Export and exit are handled as separate operating agreements.

03

Four knowledge states

defined, unknown, not_defined, not_applicable. An open value stays open and is not filled in by derivation.

openbranddefinition.orgWhat the standard means

Current version, schemas and conformance material are published at openbranddefinition.org. The standard makes decisions traceable. It is not a certification.

07Introduction

To the first approval.

A brand does not become governed through an import. The first useful milestone is concrete: brand truth is in the system, rules and prompts are bound, a real task runs through the governed path, and an eligible person makes the first approval.

  1. 01

    Establish brand truth

    Import existing OBDS material where available, otherwise author and ratify the required brand truth. Gaps are preserved rather than filled.

  2. 02

    Configure scope and control

    Markets, channels, rules, prompts and renderers, approval requirements.

  3. 03

    First governed run

    One bounded real task, with exact context, checks and evidence.

  4. 04

    First human approval

    The exact stored output, a verified actor, visible evidence. Expansion is discussed after that.

How the introduction worksDecisions become reviewable.
08Security and operation

What holds up in a security review.

We would rather say exactly what is fixed per instance than make a smooth statement that falls apart in review.

Isolation boundary
A client instance is the isolation boundary. No shared tenant environment.
Regions per instance
Data regions and subprocessors are confirmed in writing per instance before productive processing.
Human approval
Before external use, an eligible person decides on the exact stored output.
Evidence and audit trail
Execution basis, check results and approvals are recorded and can be exported.
Open format for brand truth
Brand truth sits in the open OBDS format. Export, retention and deletion are defined in the client contract and the deployment.
Security in detailBuilt in Vienna, Austria.

See a governed run from task to approval.

30 minutes on the system. We show one bounded run: which brand truth applied, what the model was called on, what was checked and who approves.

Book a demo