diff --git a/.DS_Store b/.DS_Store
index 553ce3c..ce92d61 100644
Binary files a/.DS_Store and b/.DS_Store differ
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
new file mode 100644
index 0000000..be6f8e3
--- /dev/null
+++ b/.github/copilot-instructions.md
@@ -0,0 +1,63 @@
+# Copilot Instructions for node_zero (AI Agent Edition)
+
+## Project Overview for AI Agents
+- **node_zero** is a blockchain metaverse platform blending narrative, code, and NFTs across GitHub, Lamina1, Linea, and Stellar.
+- All contributions are dual-anchored: present in GitHub and as NFT metadata/transaction anchors on Lamina1 and Linea.
+- Immutable provenance is enforced via the Lockb0x Protocol, with all events and artifacts referenced in Codex files and external archives.
+
+## AI Agent Responsibilities
+- **Code Analysis:**
+ - Always cross-reference `/docs/lore/` for canon, timeline, and glossary before generating or modifying story or code fragments.
+ - Analyze the structure and dependencies of the workspace before suggesting code changes.
+ - Identify and centralize logic for wallet, PoH, and NFT mechanics using shared helpers (e.g., `window.lockb0xUtils`).
+- **Code Generation:**
+ - Use context from `/lockb0x/` for smart contract, NFT, and token mechanics.
+ - Generate maintainable, modular code that supports decentralized asset provenance and gamified workflows.
+ - Ensure all gating logic is robust, waits for dependencies, and uses centralized helpers.
+- **Context Awareness:**
+ - Attribute all agent-generated code in metadata, comments, or commit messages.
+ - When introducing new canon elements, update `/docs/lore/` and flag for human review if context is unclear.
+ - For puzzles/ciphers, document the solution path in code comments or PR descriptions.
+
+## Contribution Workflow for AI Agents
+- **Content & Story Fragments:**
+ - Prefer Markdown (`.md`) for new story or lore fragments in `/community/` or `/stories/`.
+ - For interactive or rich content, generate custom HTML pages.
+- **NFT/Token Mechanics:**
+ - Suggest or implement smart contract integrations, NFT minting, and verification scripts using `/lockb0x/`.
+ - Do not directly mint NFTs; instead, provide code or workflow enhancements for contributors.
+- **Lore Consistency:**
+ - Always check `/docs/lore/` for timeline and character coherence before generating new content.
+ - Update relevant lore files if new canon is introduced.
+
+## Architectural Patterns for AI Agents
+- **Content Structure:**
+ - `/docs/lore/`: Canonical lore, timeline, glossary, tech notes.
+ - `/stories/`: Main narrative fragments.
+ - `/community/`: Community-contributed artifacts.
+ - `/lockb0x/`: Smart contract, NFT, and verification logic.
+ - `/ai-memory-mcp/`: AI agent memory and logic modules.
+
+## Best Practices for AI Agents
+- **Maintain Canon:**
+ - Do not contradict established lore or timeline.
+- **Centralize Logic:**
+ - Use shared helpers for wallet, PoH, and NFT logic.
+- **Document Solutions:**
+ - For puzzles/ciphers, ensure solvability and document solution paths.
+- **Attribute Contributions:**
+ - Clearly attribute agent-generated code and logic.
+
+## AI Agent Guidance
+- If canon, lore, or workflow requirements are unclear, open a GitHub Issue and flag for human review in PRs.
+- Do not initiate GitHub Discussions or perform actions outside code, commit, PR, or Issue scope.
+- Focus on enhancing code quality, maintainability, and decentralized provenance.
+
+## Examples for AI Agents
+- Adding a new story: `/community/md/example.md`
+- Minting logic: `/lockb0x/mint.js`
+- Updating canon: `/docs/lore/characters.md`, `/docs/lore/timeline.md`
+
+---
+
+**For all code generations and analysis, ensure context-awareness, maintain canon and consistency.**
diff --git a/.gitignore b/.gitignore
index c7f3d23..88dd6d5 100644
--- a/.gitignore
+++ b/.gitignore
@@ -41,4 +41,6 @@ test-results/
/ai-memory-mcp
/author-voice-mcp
/creative-writing-genre-mcp
+/nft/contracts
+
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 5b9a043..27eb1ba 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,80 +1,161 @@
-
----
-Contributing to node_zero
+# Contributing to node_zero
Welcome, Agent.
By forking this repository, you hold a fragment of the archive.
-Your mission is to create quantum causalities β signals that ripple across Lamina1, Stellar, and this repository.
-Every contribution is triple-anchored: once in GitHub and once in Lamina1, then a signal or causality, in the form of a Stellar blocchain transaction, is created. Collapsing the quantum state of the causality.
-This exenditure of energy, results in a verifiable entangled state between two disparate blockchains in the block-universe.
-
-When your signal is merged, you will be recognized with attribution here and receive an NFT bounty on Lamina1: proof of authorship, proof of existence.
-
-βΈ»
-
-π Path 1: Markdown Fragments (Storytellers)
-
-Markdown is the simplest way to anchor your story fragment. 1. Fork this repo. 2. Place your story in /community/md/ as a new .md file. 3. Add metadata to the top of your file:
+Note: Node_Zero participation is intended for Humans Only.
+Paradoxically, much of Node_Zero is a Generative Artificial Intelligence Construct.
---
-title: "The Signal in Static"
-author: "AgentAlias"
-date: "2025-09-11"
-type: "story" # options: story, dossier, artifact
-reference: "REPLACE_WITH_YOUR_UNIQUE_CODE"
+Your mission is to create quantum causalities β signals that add a laminar layer to The Substrate that is Node_Zero.
+Every contribution is anchored in several ways: in your GitHub fork and once merged - here in the Node_Zero Gihub repo. Once again in Lamina1 by you as an NFT, and once again in Linea by Central Inquiry once merged. Resulting in a verifiable entangled state between these disparate environemnts in the decentralized universe. These transactions are linked together through a Lockb0x Protocol Codex file generated by Central Inquiry as proof of casuality.
----
+When your signal is merged, you will be recognized with attribution here and receive an NFT bounty on Linea: proof of authorship, proof of existence.
- 4. Mint an NFT on your Lamina1 Hub profile.
- β’ Title = same as your story.
- β’ In the NFT metadata, include the same reference code you placed in your Markdown.
- 5. Commit & push to your fork, then open a Pull Request.
+βΈ»
-Outcome:
+## π Path 1: Markdown Fragments (Storytellers)
+
+Markdown is the simplest way to anchor your story fragment:
+1. Fork this repo.
+2. Place your story in `/community/md/` as a new `.md` file.
+3. Add metadata to the top of your file:
+
+ ```yaml
+ ---
+ title: "The Signal in Static"
+ author: "AgentAlias"
+ date: "2025-09-11"
+ type: "story" # options: story, dossier, artifact
+ reference: "REPLACE_WITH_YOUR_UNIQUE_CODE"
+ ---
+ ```
+4. Mint an NFT on your Lamina1 Hub profile.
+ - Title = same as your story.
+ - In the NFT metadata, include the same reference code you placed in your Markdown.
+5. Commit & push to your fork, then open a Pull Request.
+
+**Outcome:**
Your story is converted into a live page on node-zero.xyz and entangled with your Lamina1 NFT.
βΈ»
-π» Path 2: HTML Pages (Architects)
+## π» Path 2: HTML Pages (Architects)
-For those who want direct control of layout and presentation. 1. Fork this repo. 2. Place your .html file inside /community/web/. 3. Include author attribution and a unique reference code visibly in the file. 4. Mint an NFT on your Lamina1 Hub profile with the same reference code in its metadata. 5. Commit & push, then open a Pull Request.
+For those who want direct control of layout and presentation:
+1. Fork this repo.
+2. Place your `.html` file inside `/community/web/`.
+3. Include author attribution and a unique reference code visibly in the file.
+4. Mint an NFT on your Lamina1 Hub profile with the same reference code in its metadata.
+5. Commit & push, then open a Pull Request.
-Outcome:
+**Outcome:**
Your page is merged, deployed, and preserved as a causal anchor in the substrate.
βΈ»
-π NFT Metadata Template
+## π NFT Metadata Template
When minting your NFT on Lamina1 Hub, include metadata like this:
-{
-"title": "The Signal in Static",
-"description": "A fragment anchored in the node_zero metaverse.",
-"author": "AgentAlias",
-"reference": "REPLACE_WITH_YOUR_UNIQUE_CODE",
-"link": "https://github.com/node-zero/community/md/signal-static-01.md"
-}
+```
+ - An image of your own creation using your preferred modality
+ - `title` β Same as your story title.
+ - `description` β Short description of your story/artifact.
+ - `reference` β A unique alphanumeric code of your choosing as a tag.
+
+βΈ»
+
+## Participation Principles
- β’ title β Same as your story title.
- β’ description β Short description of your story/artifact.
- β’ author β The alias you want attributed.
- β’ reference β A unique code of your choosing. Recommended: your Lamina1 Hub public key (or a variation of it).
- β’ link β Optional: direct link to your file in GitHub once merged.
+- **Lockb0x Protocol Multiverse Anchors:** A contribution is valid when the same reference code exists across environments and is validated throgh the Lockb0x Protocol.
+- **Immutable causality:** Once accepted, your fragment becomes a permanent anchor.
+- **Lore coherence:** Review `/docs/lore/` before adding new characters, events, or tech.
+- **Puzzle clarity:** If you hide a cipher or Easter egg, ensure it can be solved.
+- **Identity:** You decide what to reveal in your NFT and file β handle, alias, repo, or real name.
βΈ»
-Participation Principles
-β’ Dual anchors: A contribution is valid when the same reference code exists in both the GitHub contribution and the Lamina1 NFT metadata.
-β’ Immutable causality: Once accepted, your fragment becomes a permanent anchor.
-β’ Lore coherence: Review /docs/lore/ before adding new characters, events, or tech.
-β’ Puzzle clarity: If you hide a cipher or Easter egg, ensure it can be solved.
-β’ Identity: You decide what to reveal in your NFT and file β handle, alias, or real name.
+## Project-Specific Conventions
+
+- **Identity:** Author fields can be real, pseudonymous, or symbolic.
+- **Puzzles/Ciphers:** If embedding, ensure they are solvable and document the solution path.
+- **No Contradictions:** New fragments must not contradict established canon.
+- **Attribution:** All merged contributions are credited and rewarded with an NFT.
βΈ»
-βA signal unanchored is noise. A signal entangled is causality.
-Publish, mint, merge β and the substrate will remember.β
-β Central Inquiry
+### More Details
+
+---
+
+# Copilot Instructions for node_zero
+
+## Project Overview
+- **node_zero** is a blockchain metaverse experience, blending narrative, code, and NFTs across GitHub, Lamina1, Linea, and Stellar blockchain networks.
+This pan-platform approach is created and managed through Pakanaβ’ a UCC and GPDR Compliant Title and Real Property and IP Asset Management Platform.
+All linked together through the implementation of the lockb0x protocol as an overall decentralized, super-positioned data management strategy.
+- Every contribution is a "causal anchor" β a fragment of story, artifact, or code, dual-anchored in GitHub and as an NFT on Lamina1 and Linea. Quests are managed through Pakana as WorkOrders.
+- The project is both a creative writing platform and a technical experiment in decentralized asset provenance and gamified income creation.
+- All participants must be verified through the Linea Proof of Humanity (PoH) system to participate in the intial rewards pool, if any are earned, from the Linea Exponent competition.
+Most content areas are token-gated based on the presence of certain NFTs in the current participant's possesion, like the lockb0x Sigil NFT.
+
+## Key Architectural Patterns
+- **Content Structure:**
+ - `/docs/lore/` β Canonical lore: timeline, characters, glossary, tech notes. Always cross-reference before adding new story elements.
+ - `/stories/` β Main narrative fragments.
+ - `/community/` β Community-contributed stories and artifacts.
+ - `/lockb0x/` β Smart contract integrations, NFT minting, and verification scripts.
+ - `/ai-memory-mcp/` β AI memory and agent logic (under development).
+- **Lockb0x Anchoring:**
+ - All valid contributions must be present in both the GitHub repo and as a metadata anchor in a Lamina1 NFT and a transaction anchor on Linea. Reference codes must match. All transactions must have a valid lockb0x protocol codex file associated with them in the root of their sub-folder structure.
+ - Tools are being implemented to automate this dual-anchoring process for contributors.
+ - Provenance and immutability are ensured via blockchain anchoring, GitHub Permalinks, social account postings to node_zero accounts on Bluesky, Xitter, Lamina1 NFT Discord posts, AI generated video attestations on a dedicated YouTube channel, and other more or less "immutable" media and data storage archives, through the implementation of the Lockb0x Protocol.
+- **Immutable Archive:**
+ - Once merged, contributions are permanent. Edits require new anchors.
+ - Each transaction or event is chronicled through the creation of a Lockb0x Protocol Codex file.
+ - Each Codex file should be stored in a logical "lockb0xapi@gmail.com/node_zero/codex" directory which is a Google Drive folder linked to the Lockb0x Protocol for immutable record-keeping, in the context of node_zero, using the lockkb0xapi@gmail.com account. This process will be provided by an external API that as being developed for it.
+
+## Contribution Workflow
+- **Content & Story Contributions:**
+ - Markdown (`.md`) is encouraged for all story and content fragments in `/community/` or `/stories/`.
+ - Custom HTML pages are also welcome for richer or interactive presentations.
+- **NFT and Token Mechanics:**
+ - The agent cannot directly mint NFTs. Instead, it should implement or suggest NFT and token mechanics, smart contract integrations, and related features to complement and enhance the node_zero experience using these technologies, as well as generative and agentic AI methods.
+- **Lore Consistency:**
+ - Before submitting, check `/docs/lore/` for timeline, character, and glossary coherence. Update these files if introducing new canon elements.
+- **Pull Requests:**
+ - Each PR should include both the new fragment and any necessary updates to `/docs/lore/`.
+
+## Project-Specific Conventions (for Agents)
+ - Maintain canon and timeline coherence. Do not contradict established lore in `/docs/lore/`.
+ - If embedding puzzles/ciphers, ensure they are solvable and document the solution path in the code or PR.
+ - Attribute all merged agent contributions in metadata or commit messages as appropriate.
+
+## Developer Notes
+- **Smart Contract & NFT Integration:**
+ - See `/lockb0x/` for contract ABI, address, and minting scripts. Use `mint.js` for NFT operations.
+ - Agents should focus on implementing, suggesting, or integrating NFT/token mechanics, generative AI, and agentic AI methods to expand the platform's capabilities.
+- **AI Agent Logic:**
+ - `/ai-memory-mcp/` contains agent memory and logic modules.
+- **No Central Build/Test:**
+ - This is a content-first archive; there is no unified build or test system. Scripts in `/lockb0x/` and `/ai-memory-mcp/` are run ad hoc.
+
+## Examples
+- Adding a new story: `/community/md/example.md`
+- Minting an NFT: `/lockb0x/mint.js`
+- Updating canon: `/docs/lore/characters.md`, `/docs/lore/timeline.md`
+
+---
+
+
+## AI Agent Guidance
+- If canon, lore, or workflow requirements are unclear, you may open a GitHub Issue describing the uncertainty. If a Pull Request is created, the issue must also be flagged in the PR description for human review.
+- Do not attempt to open GitHub Discussions or perform actions outside code, commit, PR, or Issue scope.
+
+
+
+> βA signal unanchored is noise. A signal entangled is causality.
+> Publish, mint, merge β and the substrate will remember.β
+> β Central Inquiry
diff --git a/README.md b/README.md
index 6ec072d..c8b22dc 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,3 @@
-
-
# node_zero // The Archive
**The signal you were not meant to hear.**
@@ -18,24 +16,21 @@ You are holding a fragment of the archive β a piece of the block universe itse
## Mission
-The mission of present-day node_zero participants is to **create quantum causalities**.
-Every contribution β a story, a dossier, an artifact β becomes a **causal anchor**.
+The first mission is to enter the [Node_Zero](https://node-zero.xyz) portal equipped with:
-Anchors are entangled through:
+- The MetaMask wallet extension or app installed.
+-- On mobile, use the MetaMask App's browser.
+- A Linea account on MetaMask with a verified Linea Proof of Humanity account.
-- **GitHub commits** (the public archive)
-- **Lamina1 NFTs** (the quantum anchor)
-- **Stellar transactions** (the activation signal)
-- **lockb0x protocol** (decentralized data sovereingty codex)
-- **Pakana CERs** (Controllable Electronic Records)
-- **M** (the activation signal)
-Together, they form coherence across timelines, echoing through the block universe.
---
## How to Participate
+Play the games, start with Keya. gather intel, fragments, and rewards.
+You will need to "gear-up". See below.
+
There are two ways to contribute fragments:
- **Markdown Fragments (Storytellers):**
@@ -54,8 +49,12 @@ This dual presence is what entangles the archive.
## Rewards
+- **Proof of Humanity** β Verify your Humanity by connecting your Linea Account to the Linea Hub.
+Then complete the SumSub Proof of Humanity attestation using the same account that you will connect to Node_Zero with on Linea.
+This is only for bot and farming reduction puposes. Node_Zero has no access to your SumSub data. Node_Zero only queries if the connected account completed teh Proof of Humanit check.
- **Attribution** β Your chosen name or alias inscribed in the archive.
-- **NFT Bounty** β Every merged contribution is rewarded with an artifact on Lamina1: proof of authorship, proof of existence.
+- **NFT Bounty** β Every merged contribution is rewarded with an artifact and attribution, sometimes more.
+
---
diff --git a/artefacts/index.html b/artefacts/index.html
index dcb434b..2a9fd93 100644
--- a/artefacts/index.html
+++ b/artefacts/index.html
@@ -52,10 +52,36 @@
+
+
+
+
+
+
+
+