Awakened Imagination: The Path to Abundance

Mission: To secure the Age of Abundance through the development of outer space, healing the biosphere, and promoting a sustainable, peaceful, and strategic presence for all sentient life.

Welcome to the official repository of the Awakened Imagination Group of Projects. This site translates high-level orbital development vision into tactical execution logs.

🗺️ Project Architecture

The project is structured around four primary pillars, each with a dedicated interactive hub and tactical documentation:

graph TD
    subgraph "Public Interface (GitHub Pages / Surge)"
        A["Home (index.html)"] --> B["The Effort (effort.html)"]
        A --> C["Imagine (imagine.html)"]
        A --> D["Master Plans (plans.html)"]
    end
    
    subgraph "Tactical Ledgers (Markdown Hub)"
        D -->|View Plan| L1["ledger-stewardship.md"]
        D -->|View Plan| L2["ledger-foundations.md"]
        D -->|View Plan| L3["ledger-life-support.md"]
        D -->|View Plan| L4["ledger-prosperity.md"]
    end
    
    subgraph "Requirement & Alignment"
        R["REQUIREMENTS.md"] -.->|Technical Blueprint| D
    end

Loading

🌐 Site Overview

• Home: main page highlighting the primary areas of interest +
• The Effort: TRL 1 designs of autonomous swarm units (AMUs) and some other designs.
• Imagine: original vision
• Token Dashboard: governance token dashboard for Space Infrastructure Token (SIT)
• Master Plans: "back of the envelope" plans.

🚀 Tactical Ledger Integration

The Plans page acts as a living bridge between the abstract vision and tactical execution. Every plan card on the site maps directly to a Tactical Ledger in this repository:

1. Orbital Stewardship: Security, hygiene, and debris mitigation (Kessler Syndrome prevention).
2. Interplanetary Foundations: Deep space industrial backbone and Interplanetary Transport Network (ITN).
3. Planetary Life Support: Orbital health span research and bio-scarcity elimination (ISS decommissioning alignment).
4. Global Prosperity: Transitioning heavy industry off-world to allow Earth's biosphere to heal.

🏗️ Hierarchical Organization

We've recently restructured the project with a clearer hierarchy to improve navigation and execution:

Core Tiers

• Tier 1: Core Foundation - Essential infrastructure and governance
• Tier 2: Infrastructure Development - Building the backbone for operations
• Tier 3: Application & Expansion - Implementation and scaling activities

Status Tracking

Each component tracks its progress with these statuses:

• Conceptual - Initial idea phase
• In planning - Detailed planning underway
• Being developed - Active development
• Implemented - Completed and operational
• Completed - Fully finished

Priority Levels

• High - Critical path items requiring immediate attention
• Medium - Important but not blocking other developments
• Low - Valuable but lower urgency items

For detailed roadmap information, see our ROADMAP.md file.

🛠️ The Architecture of Abundance (AMUs)

Our foundational technology is the 3-stage AMU (Autonomous Manufacturing Unit):

• Self-Replication: Designed for exponential scale.
• Reorientation: Capable of on-orbit re-tasking for diverse manufacturing needs.
• TRL Target: We are currently bridging the gap from TRL 1 to TRL 9 for orbital deployment.

🪙 Space Infrastructure Token (SIT)

The Space Infrastructure Token (SIT) is the governance token for the Awakened Imagination ecosystem. It enables collective ownership and decision-making for space infrastructure development.

• Purpose: Governance and utility token for space infrastructure projects
• Total Supply: 1,000,000,000 SIT (1 billion)
• Standard: ERC-20 compatible on Ethereum
• Features: Governance voting, staking rewards, access rights

Token Dashboard

View your token balance, governance proposals, and voting power at the Token Dashboard.

Smart Contracts

• Token Contract: EnhancedSpaceInfrastructureToken.sol in /contracts/
• Test Coverage: Available in /test/
• Deployment: Configured for mainnet via Hardhat

BSC Testnet Token

For testing smart contracts without real costs, we've created a TestToken with 10 billion supply:

• Contract: contracts/testtoken/TestToken.sol
• Tests: test/TestToken.js
• Deployment Script: scripts/deploy-testtoken-bsc.js

Quick Start:

# Get faucet info
npm run faucet

# Deploy to BSC Testnet
npm run deploy:bsc

# Verify on BSCScan
npm run verify <contract-address>

Prerequisites:

1. MetaMask connected to BSC Testnet (Chain ID: 97)
2. Test BNB from faucet (see npm run faucet)
3. .env file with PRIVATE_KEY

🤝 Join the Effort

This project follows the Wikipedia Model—it is a collaborative, radically transparent public benefit ecosystem. We are currently seeking:

• Lead Ethicists & Habitat Designers
• Geneticists & Astrobiologists
• Remote Operations Teams (Australia/Canada expertise)

Support our mission via GitHub Sponsors.

📝 Contributing Guidelines

This is an open-source project and we welcome contributions from the community!

To get started:

• Read our CONSTITUTION.md for the project's philosophical and organizational framework
• Read our CONTRIBUTING.md for detailed contribution guidelines
• Review our CODE_OF_CONDUCT.md to understand our community standards
• Check out the issue templates for consistent issue reporting
• Use the pull request template when submitting changes

Note: We are currently deciding on an open-source license. See the license decision issue for details.

🏗️ Wikinomics Code Structure

Disclaimer: This code has yet to be verified by the project developers.

This repository implements a decentralized ownership and governance system for space infrastructure, inspired by Don Tapscott's wikinomics principles. Here's how it works:

Core Principles: The "Brick and Documentation" Framework

*(From session with Gemini via phone: 04-12-2026 - "Architecting Modular Systems: The 2026-04-12 Blueprint")

1. The "Brick" (Modular Atomic Units)

Instead of writing long, intertwined scripts, we build "Bricks" - atomic, single-task units that serve as reusable components:

• Definition: Every function or class is designed to perform one task exceptionally well.
• Purpose: These bricks act as a system of reusable components. Once built and tested, they become "solved problems" that can be assembled into larger, complex projects without rewriting logic.
• The Goal: Shifting from a "hacker" mindset to an "architect" mindset—building a high-leverage library rather than one-off tools.

2. Documentation as the "Contract"

Documentation isn't just an afterthought; it's the API contract between you and the machine:

• Strict Type Hints: Essential for the code to be self-documenting and for AI agents to understand exactly what data is moving through the system.
• Docstrings: Every "Brick" must have a clear description of its intent, inputs, and outputs.
• Standard Operating Procedures (SOPs): This is a global protocol for all repositories, ensuring any technical asset follows the same high-standard, repeatable pattern.

3. The Human/AI Orchestration

With perfect documentation and modular "Bricks," it becomes exponentially easier for an AI (or another developer) to help build or refactor:

• You provide the high-level architecture, and the "Bricks" handle the heavy lifting.
• This creates a foundation of certainty so that when scaling into complex projects (space industry, AI ethics), the base layer of your tech stack is rock solid.

Implementation Structure

The project follows a decentralized architecture with these key components:

The project follows a decentralized architecture with these key components:

1. Smart Contracts for Collective Ownership

   • contracts/SpaceInfrastructureToken.sol - Ethereum smart contract for token-based ownership and governance
   • Enables transparent, code-enforced ownership shares and voting rights
   • Anyone can verify and participate in governance

2. Open Source Collaboration

   • All hardware designs and software are open source
   • GitHub Actions automatically validate AMU designs (.github/workflows/validate-designs.yml)
   • IPFS storage for immutable, versioned blueprints (scripts/ipfs-storage.js)
   • Contribution tracking in package.json rewards community members with ownership shares

3. Decentralized Resource Allocation

   • scripts/resource-allocator.py - Transparent resource distribution based on ownership shares
   • Blockchain-based dividend distribution ensures fair compensation
   • All transactions are publicly verifiable

4. Automated Validation

   • scripts/validate-design.js - Validates AMU designs against technical requirements
   • Ensures quality and safety while enabling open collaboration
   • Design files stored on IPFS for permanent, tamper-proof records

5. Transparent Governance

   • Ownership shares grant voting rights on project decisions
   • Proposals and voting are managed through smart contracts
   • All actions are recorded on the blockchain for accountability

This structure enables true collective ownership of space infrastructure, where anyone can contribute, own, and govern. The code is fully open source, allowing anyone to verify, fork, or contribute to the project.

1. Smart Contracts for Collective Ownership

• contracts/SpaceInfrastructureToken.sol - Ethereum smart contract for token-based ownership and governance
• Enables transparent, code-enforced ownership shares and voting rights
• Anyone can verify and participate in governance

2. Open Source Collaboration

• All hardware designs and software are open source
• GitHub Actions automatically validate AMU designs (.github/workflows/validate-designs.yml)
• IPFS storage for immutable, versioned blueprints (scripts/ipfs-storage.js)
• Contribution tracking in package.json rewards community members with ownership shares

3. Decentralized Resource Allocation

• scripts/resource-allocator.py - Transparent resource distribution based on ownership shares
• Blockchain-based dividend distribution ensures fair compensation
• All transactions are publicly verifiable

4. Automated Validation

• scripts/validate-design.js - Validates AMU designs against technical requirements
• Ensures quality and safety while enabling open collaboration
• Design files stored on IPFS for permanent, tamper-proof records

5. Transparent Governance

• Ownership shares grant voting rights on project decisions
• Proposals and voting are managed through smart contracts
• All actions are recorded on the blockchain for accountability

This structure enables true collective ownership of space infrastructure, where anyone can contribute, own, and govern. The code is fully open source, allowing anyone to verify, fork, or contribute to the project.

📁 Repository Structure

asi.surge.sh/
├── contracts/              # Smart contracts for governance
│   └── SpaceInfrastructureToken.sol
├── scripts/                # Utility scripts
│   ├── ipfs-storage.js     # IPFS-based blueprint storage
│   ├── validate-design.js  # Design validation
│   └── resource-allocator.py  # Resource allocation
├── .github/                # GitHub workflows and templates
│   ├── workflows/
│   │   └── validate-designs.yml
│   └── ISSUE_TEMPLATE/
│       ├── bug_report.md
│       ├── feature_request.md
│       ├── license_decision.md
│       └── pull_request.md
├── README.md
├── CONTRIBUTING.md
├── CODE_OF_CONDUCT.md
├── package.json           # Contribution tracking
└── ...

🛠️ Development Setup

Prerequisites

• Node.js 18+ and npm
• Docker (optional, for containerized development)

Installation

1. Clone the repository:

   git clone https://github.com/stellardreams/asi.surge.sh.git
   cd asi.surge.sh

2. Install dependencies:

   npm install

3. Compile contracts:

   npx hardhat compile

Running Tests

# Run all tests
npx hardhat test

# Run specific test
npx hardhat test test/SpaceInfrastructureToken.test.js

Local Development with Docker

# Start development environment
docker-compose up

# Run tests in container
docker-compose run hardhat npm test

Smart Contract Development

• Edit contracts in contracts/ directory
• Add tests in test/ directory
• Configure Hardhat in hardhat.config.js
• Use OpenZeppelin contracts for security best practices

Contributing

We welcome contributions from the community! Please follow our CONTRIBUTING.md guidelines and review our CODE_OF_CONDUCT.md before submitting pull requests.

---

Vision co-conceived by Adeel Khan