Skip to content

HOW-TO-SUBMIT.md

Latest commit

 

History

History
117 lines (73 loc) · 3.75 KB

HOW-TO-SUBMIT.md

File metadata and controls

117 lines (73 loc) · 3.75 KB

HOW TO SUBMIT — Plain English Guide

You don't need to be a developer to use the Sovereign Trace Protocol. You just need a GitHub account and something worth sealing.

Step 1 — Create a Free GitHub Account

Go to github.com and sign up for a free account. That's it. No payment required to submit a trace.

Step 2 — Go to the Issues Page

Click this link: https://github.com/AionSystem/SOVEREIGN-TRACE-PROTOCOL/issues/new/choose

You will see a list of templates. Pick the one that fits what you want to seal.

Step 3 — Pick Your Template

If you want to seal... Use this template
An AI output failure 01 — AI Failure
A research hypothesis 02 — Research Priority
A document you received 03 — Evidence Chain
A song, poem, design, or creative work 04 — Creative Priority
A clinical or hospital record 05 — Clinical Record
A project scope or agreement 06 — Scope Anchor
Anything else 07 — General Trace
A prediction about the future 08 — Foresight Seal
A link between two sealed records 09 — WEBEATER Link
A certified audit request 10 — Audit Request

Not sure? Use 07 — General Trace. It works for everything.

Step 4 — Fill in the Form

Every form asks for the same core things:

  • Title — follow the format shown in the placeholder text
  • Your name — optional, but becomes part of the permanent record
  • Date — the date the moment happened, format: YYYY-MM-DD
  • Your trace entry — write exactly what is true. Present-moment. No narrative arc. Specific enough to be contested.
  • Declaration checkboxes — check both. You are affirming this is accurate and you understand it cannot be changed.

Then click Submit new issue.

Step 5 — Wait for the Seal

After you submit, the protocol processes your entry automatically.

Within minutes you will see a comment posted on your issue that looks like this:

✅ SOVEREIGN TRACE SEAL — COMPLETE

Ledger ID:    STP-GENERAL-TRACE-2026-03-09-000005
SHA-256:      a63c4f28cf7c3f2c63c220d61980...

Triple-Time Stamp:
📅 Gregorian:  March 9, 2026
🌑 Hebrew:     20 Adar 5786
🌀 Dreamspell: Day 3, Solar Moon 9/13

Status: SEALED — permanent, tamper-evident, unalterable.

Your Ledger ID is your receipt. Copy it and keep it.

What Makes a Good Trace Entry

Good:

"Submitted proposal to client on March 9, 2026. Scope: 10 AI output reviews, delivery within 72 hours, fee $2,500. Client: [name]. This is the agreed scope before work begins."

Good:

"Hypothesis: current transformer architectures cannot maintain persistent identity across sessions without external session architecture. Sealed before any experiment or publication."

Not good:

"Something important happened today."

The seal is only useful if the content is specific enough to be contested. Vague entries seal nothing meaningful.

Can I Edit My Submission After Filing?

No. That is the point.

The seal binds your exact text to the exact moment you submitted it. Any change — even one character — breaks the seal. If you need to add context, file a new trace and reference the original Ledger ID.

Is This Free?

Submitting a trace through GitHub Issues is free. The seal, the ledger entry, and the SHA-256 proof cost nothing.

Certified audits (Tier 1–4) are paid services. See CERTIFICATION.md for pricing.

I Don't Understand Something

Email: aionsystem2026@gmail.com

Sovereign Trace Protocol · FROZEN-2.0 · Sheldon K. Salmon · March 2026 The stamp is permanent. The stamp is the resolution.