DragonSourceRelease 11.1

A new horizon for security

Skyfall

Security from signal to prototype.

Four guards protect the code today. Eight safeguards shape what comes next. Designed first for Astraeus, with a person in command throughout.

Enter the Security Lab Explore the safeguards
Explore the release
SkyfallRelease 11.1

00 / Release overview

A clear line between now and next.

Skyfall / 11.1

Built on evidence. Clear about what comes next.

01 / Today · The Security Lab

Inside the network.

Every connection tells a story. Every layer changes it.

  • Real mechanisms. Fictional data.
  • Friction is useful. Know the boundary.
Guards
4 / 4 live
Where they work
Client side, in your browser
Sample
Fictional data
Challenge the protection
The protection stack4 / 4 on · select a guard to trace it
  1. Live in the Lab

    Source transforms hide structure. Switch it off in the Lab and read the engine.

    Layer 01 of 04 · all four active

These layers raise the cost of copying and casual inspection. Secrets belong on the server.

02 / Core · Across the stack

Every operator holds its own line.

Skyfall runs across the board. At the front of the stack, each core operator carries its own security initiative, told here by purpose, never by mechanism.

01 / 04

Core 01 / Authorize

Athos

The Ring of Power.

In design

Authority lives with people. Athos is where it is held, and where it is handed out, sparingly.

  1. 01Authority belongs to people, never to a process.
  2. 02Consequential work starts from a mandate a person signs: one purpose, a narrow scope, a set expiry.
  3. 03Nothing downstream can grant itself more than its mandate gave it.
Schematic · illustrativeAuthority radiates from a person and stops at its ring.

03 / Next · What Skyfall is becoming

Eight safeguards.

Astraeus moves work from a market signal toward a physical prototype. The four guards protect the code where it runs; these eight are designed to protect the work as it moves, with controls that grow stronger the closer the work gets to the physical world.

In design · not yet in service
Four guards
Live · the code
Eight safeguards
In design · the handoffs
Implemented first
Astraeus
01 / 08
S01 · IdentityIn design

Zero-trust authentication

Specevery request · every time · least privilege

Every platform verifies the one talking to it, every time. Being inside Astraeus earns no trust on its own, and each service holds only the permissions its job needs.

Acts at
Verify
Implemented first
Astraeus
Reference
NIST SP 800-207

Standards citedNIST SP 800-207 · zero trust IETF RFC 9449 · replay-resistant proofs NIST SP 800-82 · operational technology

Next · how they hold

Designed to hold together.

No safeguard works alone. The notes behind the design, and the record every handoff is designed to keep.

Design notes

  • A single-use code can still be relayed in real time by someone in the middle, so it never works alone: authenticated identity, request binding, short expiry and independent permission checks hold together.

Every handoff, on the record

  1. Prepared
  2. Authorized
  3. Accepted
  4. Executing
  5. Completed

or it ends failed, canceled, rejected or quarantined

04 / Method · The Pipeline System

Astraeus

Market signal to physical prototype, in minutes rather than months.

Six platforms designed to turn a market signal into finished work, one defined handoff at a time, with a person still signing off on what matters.

Reveal · Date to be announced

ScopePrivate-sector industry analysis and rapid prototyping for manufacturing. Not a military or government application. The mythology is entertainment.

Read the invitation
Handoff statejob sample-0042 · blueprint r3
Executions 1Illustrative

05 · CompletedThe result comes back verifiable and on the record.

Walk through one handoff

04 / Inside Astraeus · The first implementation

One handoff.

Follow one prototype through the pipeline and watch each safeguard engage. Run it clean, or cut the line halfway and see why nothing runs twice.

Design walkthrough
Simulation · illustrative

Sender

Where the work is planned and approved

Idle · ready to plan

Resends
0
Physical build
Not requested
StateIdle
  1. Prepared
  2. Authorized
  3. Accepted
  4. Executing
  5. Completed
Link up

Waiting · press Run

Receiving engine

Where the approved work runs

Idle · nothing authorized

Executions
0
Execution ID
—
  1. 01Plan
  2. 02Approve
  3. 03Authorize
  4. 04Verify
  5. 05Return
  6. 06Gate

Six steps, one handoff. Press Run, or Step through it.

Event stream0 events

  1. Waiting · press Run

Every handoff carries one versioned manifest

Change the blueprint and a new revision is born. An approval never silently carries over to it.

Seal verified
Try it: edit the blueprint after it was approved.
manifest.json · identityfictional sample
{
  "project": "sample-bracket",
  "job": "job-0042",
  "revision": "r3",
  "material": "PA12",
  "authorized_by": "reviewer · a person"
}

05 / Proven · The test program

Before any claim.

Each safeguard is tested against the ways it could fail. Every test writes down the safe result it expects before it runs, then records what actually happened.

Planned · 8 tests · 0 run

  1. Expected safe result

    The second request finds the existing execution. Nothing runs twice.

    Observed

    Pending · not yet run

Proven · the bar

What a pass means.

Five outcomes every passing run has to show. A pass proves that workflow, not every workflow: claims grow only as the evidence does.

  • Identity and state hold across every handoff
  • Every unauthorized action is rejected
  • A dropped connection recovers safely
  • Nothing physical is ever made twice
  • The result leaves a traceable record

06 / Engines · Where the work is made

Made under guard.

Three engines are being built to turn approved work into results: a part designed, a part made, a game world produced. Each carries its own Skyfall initiative, shaped by what it makes and how near that comes to the physical world.

The three engines3 engines · select one to bring it forward

  1. Engine 01 / Fabrication

    PROTO

    Sealed by design.

    In design

    PROTO shapes a precise part from its specification. Skyfall keeps an approved design exactly as it was approved.

    1. 01The same specification always yields the same part, so any design can be rebuilt and checked.
    2. 02An approved design is sealed whole: change one dimension or material, and the approval no longer holds.
    3. 03A finished model is a proposal, never a work order.
    Digital · one step from the physical

  2. Engine 02 / Manufacturing

    Mophase

    Made once.

    In design

    Mophase plans how a finished part gets made. It works nearest the physical world, so it holds the strongest guard.

    1. 01Checking that a part can be made never authorizes making it: a person approves every job.
    2. 02Every job keeps one identity, so a dropped connection can never make the same part twice.
    3. 03Machines keep their own safety, apart from any software. A conflict means a safe stop.
    Physical · the strongest guard

  3. Engine 03 / Game production

    Oasis

    Open books.

    Principle

    Oasis takes a creative request and works out how to produce it. Skyfall keeps every run planned, priced and on the record.

    1. 01Each request becomes a plan first: the tools, the order and the cost, set out in advance.
    2. 02A person approves the plan and its price. Without that yes, nothing runs.
    3. 03Every run keeps its log, so what was made, and why, can always be traced.
    Virtual · furthest from the physical

Schematics are illustrative. All three engines are in active development, and in each the final say is a person's.

07 / Framework · The whole of Skyfall

Guarded in depth.

Skyfall is not one wall. It is rings around the work the engines make: guards around the code, safeguards around every handoff, operators holding their lines, and people holding the outermost ring. Here is the whole of it, and what each part stands against.

Select a ring to open it.

What it defends against

Every threat, answered.

Each threat the framework is built against, the part of Skyfall that answers it, and the test that will prove it.

  1. Threat 01 · answered by

    The four guards

    Guards · around the codeLive

    Conceal, mutate, respond, seal: the code is hidden, varied, defended and sealed where it runs.

    ProofLive now in the Security LabChallenge the protection

Threat 01 · answered by

The four guards

Guards · around the codeLive

Conceal, mutate, respond, seal: the code is hidden, varied, defended and sealed where it runs.

ProofLive now in the Security LabChallenge the protection

08 / Always · The rules it answers to

Under human command.

Six principles shape every safeguard: people hold the authority, and the system holds the line.

  1. 01Peopleset the objectives and the bounds
  2. 02AIdevelops and weighs the options, inside them
  3. 03Enginesturn approved work into verifiable results
P01

People decide

People set the outcomes that are allowed, and keep the final say.

01 / 06

The principle behind Skyfall

The closer work gets to the physical world, the stronger the guard.

Explore what protects the code today. Discover what comes next.

Enter the Security Lab Discover Astraeus
Back to the beginning