01
Step 01
Source
Documents, notes, plans, specs, links or structured files give Nolta the raw material for a new universe.
Blueprints
Govern how work becomes context.
Blueprints are persistent operating contracts for Nicky-assisted universe creation, scoped AI execution and human-reviewed change.
They tell Nolta what kind of work it is looking at, how it should become a living universe, which execution types are allowed and what must be reviewed before anything becomes trusted context.
The Blueprint is the scope firewall for the universe.
Structuredefined
Rulesactive
Executiongated
Reviewrequired
Not a static template
A Blueprint is the operating contract for a Nolta universe.
A template copies a shape. A Blueprint defines how a type of work should be understood, created, used and protected over time. It separates the generic Nolta engine from the domain-specific rules that make a universe useful.
02
Step 02
Blueprint
A persistent operating contract tells Nolta how this kind of work should be interpreted, structured and governed.
03
Step 03
Nicky proposal
Nicky applies the Blueprint, asks the necessary questions and proposes Universes, Galaxies, Planets, Satellites, links and gaps.
04
Step 04
Approval
Humans review, edit and approve before Nolta creates trusted context and records how the universe was born.
Assisted universe creation
From source material to a reviewed universe.
Nolta can start from existing knowledge: documents, plans, research files, creative briefs, technical scope or structured imports. Nicky reads the source, applies the active Blueprint and proposes how the work should become a universe.
The proposal can include Universes, Galaxies, Planets, Satellites, links, missing questions and alternate structure choices. The user reviews the proposal before Nolta creates trusted context.
Persistent governance
The Blueprint stays with the universe after creation.
This is the important part: Blueprints are not only creation helpers. They become persistent scope firewalls for the universe. They guide context packaging, allowed execution types, provider policy, documentation requirements, cost scope and review gates.
That prevents the execution block from becoming a giant free-for-all prompt box. When requested work does not fit the active Blueprint, Nolta should block it before execution and explain why.
Blueprint gate
Not in the rules? It does not run.
Missing documentation, wrong scope, disallowed provider, oversized context package, weak evidence or irrelevant execution request can all be stopped before AI work begins.
Scope before cost. Rules before execution. Review before trust.What a Blueprint controls
Rules that shape both context and execution.
The same Blueprint that helps Nicky create the universe should later help Nolta decide what context is relevant, what work is allowed and what review is required.
01
Structure
Define the shape of the universe
A Blueprint describes which structures are allowed, what Galaxies and Planets should represent, and which choices require confirmation.
02
Context
Control what gets packaged
It guides what context should be included, excluded, weighted, referenced or treated as missing before AI work starts.
03
Execution
Block irrelevant AI work before it runs
If an execution request does not fit the active Blueprint, Nolta can stop it before cost, noise or unsafe context expansion happens.
04
Review
Require the right human approval
Blueprints can define evidence expectations, review requirements and proposal gates before approved changes become part of the record.
Example clarification
I found two valid galaxy structures in the source.
Should Nolta organize this universe by source-defined areas or by sequence unit?
- Choose source-defined areas when the source already lists the major context buckets.
- Choose sequence-first when each episode, chapter, phase, sprint, module or research stage should become its own galaxy for scoped execution.
Nicky should ask, not guess
When structure changes meaning, the user decides.
A source can support more than one valid universe structure. A creative production may be organized by source-defined areas or by episode sequence. A research project may be organized by hypotheses or attempts. A software project may be organized by modules or release slices.
A good Blueprint makes those choices visible. Nicky can recommend a path, but the human approves the structure before Nolta creates the world.
Reusable patterns
One engine, many kinds of work.
Blueprints keep the Nolta core generic while making domain-specific context creation and execution practical, repeatable and reviewable.
Creative production
Turn a show bible, episode outline or game concept into a governed universe for scoped writing, production and review work.
Research work
Structure hypotheses, evidence, failed paths, attempts, findings and unresolved questions without losing the reasoning trail.
Software delivery
Translate modules, releases, risks, test evidence and implementation tasks into context AI can work from safely.
Engineering missions
Create a living mission structure from plans, assets, dependencies, decisions, documentation and verification needs.
The simple version
A Blueprint tells Nolta how this universe is allowed to work.
Nicky uses it to create the first proposed universe. Nolta keeps using it to package context, gate executions, require review and preserve the audit trail. Rules before execution. Review before trust.