VyuhBlueprint

VYUH BLUEPRINT / THE CONNECTED APPLICATION ENGINE

Draw the model.
Build the connected world.

One model.
Many possibilities. ↙

Define your business model. Extend it through features. Build applications that share the same data and rules.

Learn the core concepts Start building
One model. Connected applications.Domain knowledge enters Blueprint. One branch produces shared identity, policy, runtime and evidence services. A second branch supports Directory, Docs, Qualify, Operations and Case Management applications. These applications share governed relationships.Your domainpeople · work · rulesBlueprintidentity + meaningactions + proofShared operational foundationIdentity · Policy · Runtime · EvidenceConnected applicationsDirectory · Docs · QualifyOperations · Case Managementsame contractdeclare once, carry meaning through →One model. Connected applications.Your domain enters Blueprint. Blueprint branches into a shared operational foundation and connected applications. The foundation and applications use the same contract.Your domainpeople · work · rulesBlueprintidentity + meaningactions + proofShared foundationIdentity · PolicyRuntime · Evidencesame contractConnected applicationsDirectory · Docs · QualifyOperations · Case Management
Conceptual application composition. Each product still supplies its declarations, bindings, and integrations.
DRAWING 001 / SYSTEM OVERVIEWDART → CONTRACT → RUNTIME → APPLICATIONS

THE PHILOSOPHY

Start with what things mean.

People, equipment, materials, and operations belong to the same world. Let your applications share that understanding.

01

Model the real world.

Give things clear identities and connect them with meaningful relationships. A batch is made on equipment, from material lots, by people.

Explore
02

Extend without copying.

Use descriptors to add facets and behavior to entities owned by other modules. A cleaning module adds a cleaning facet to equipment it does not own.

Explore
03

Keep the history intact.

Record what changed, who changed it, and which revision applied. A batch release names its signer and the master batch record it ran against.

Explore

FROM DECLARATION TO OPERATION

Meaning is the thread.
Proof closes the loop.

Assemble the model, generate its contracts, and run actions with shared rules. Every outcome carries its evidence.

The same release rule governs the button on the screen, the API call, the database transaction, and the audit record.

See the behaviour loop
  1. DeclareEntities · facets · relationships · actions
  2. CompileStorage · protocol · metadata · receipts
  3. ExecutePlan · preflight · transaction · effects
  4. ExplainDecisions · revisions · evidence · replay

THE THREE PLANES

Three questions, kept apart.

What the application means, how each site uses it, and what actually happened are answered in different places.

Declaration

What can the application do?

A batch has a release action that needs a QA signature.

Configuration

How does this site use it?

This plant chooses who may release batches and connects its own services.

Execution

What happened?

A QA reviewer released batch B-2417 at 14:32 and signed with the meaning “Approved”.

Understand the three planes

BUILD WITH BLUEPRINT

A clear path from setup to running.

Run your workspace

Check setup, start servers, and launch your app with the Blueprint CLI.

Use the CLI →

Blueprint is pre-production. Verify behavior in your target environment.