refactor: migrate Markdown to AsciiDoc

.claude/PROJECT.adoc

@@ -0,0 +1,33 @@
+== The-Nash-Equilibrium - Claude Code Instructions
+
+This repository contains the The-Nash-Equilibrium project.
+
+=== Project Structure
+
+....
+the-nash-equilibrium/
+├── .claude/         # AI assistant instructions
+├── .git/           # Version control
+├── .gitignore      # Git ignore rules
+├── .editorconfig   # Editor configuration
+└── ...             # Project files
+....
+
+=== Build Commands
+
+Refer to project-specific documentation.
+
+=== Coding Conventions
+
+* Follow hyperpolymath standards
+* All code must have SPDX license headers
+* Use approved languages only (see CLAUDE.md)
+* Document all non-obvious decisions
+
+=== Security
+
+* No hardcoded secrets
+* All secrets through environment variables or secret management
+* SHA-pinned dependencies where applicable
+* HTTPS only, no HTTP URLs
+* No MD5/SHA1 for security purposes

ARCHITECTURE.adoc

@@ -0,0 +1,48 @@
+== Architecture
+
+=== Overview
+
+This repository follows a modular, maintainable architecture designed
+for clarity, scalability, and long-term sustainability.
+
+=== Directory Structure
+
+....
+.
+├── src/           # Source code
+├── tests/        # Test suites
+├── docs/         # Documentation
+├── scripts/      # Utility scripts
+├── config/       # Configuration files
+├── LICENSE       # License file
+├── LICENSES/     # Full license texts
+└── README.adoc   # Project documentation
+....
+
+=== Design Principles
+
+* *Separation of Concerns*: Each module has a single responsibility
+* *Testability*: Code is written to be easily testable
+* *Documentation*: All public APIs are documented
+* *Configuration*: Environment-specific settings are externalized
+
+=== Dependencies
+
+* External dependencies are minimized and clearly declared
+* Version pinning is used for reproducibility
+
+=== Security Considerations
+
+* Sensitive data is never committed to the repository
+* Secrets are managed through environment variables or secure vaults
+* Regular dependency audits are performed
+
+=== Maintainability
+
+* Code follows consistent style guidelines
+* Pull requests require review and CI checks
+* Issues and discussions are tracked transparently
+
+'''''
+
+_Last updated: 2026-07-18_

CHANGELOG.adoc

@@ -0,0 +1,9 @@
+== Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on https://keepachangelog.com/en/1.1.0/[Keep a
+Changelog], and this project adheres to
+https://semver.org/spec/v2.0.0.html[Semantic Versioning].
+
+=== [Unreleased]

CONTRIBUTING.adoc

@@ -0,0 +1,9 @@
+== Contributing
+
+[arabic]
+. Fork the repository
+. Create a feature branch
+. Ensure SPDX headers on all files
+. Submit a pull request
+
+*Author:* Jonathan D.A. Jewell j.d.a.jewell@open.ac.uk

GOVERNANCE.adoc

@@ -0,0 +1,60 @@
+== Governance
+
+=== Overview
+
+This project is governed by the following principles and structures to
+ensure transparent, inclusive, and effective decision-making.
+
+=== Roles and Responsibilities
+
+==== Maintainers
+
+Maintainers are responsible for: - Reviewing and merging pull requests -
+Managing releases and versioning - Ensuring code quality and standards -
+Triaging issues and bug reports - Community engagement and support
+
+==== Contributors
+
+Contributors are expected to: - Follow the code of conduct - Submit
+well-documented pull requests - Write tests for new functionality -
+Maintain existing tests - Update documentation as needed
+
+=== Decision Making
+
+==== Minor Changes
+
+* Can be made by any maintainer
+* Include bug fixes, documentation updates, dependency updates
+
+==== Major Changes
+
+* Require discussion in issues or pull requests
+* Include new features, architectural changes, API changes
+* Need approval from at least 2 maintainers
+
+==== Breaking Changes
+
+* Require RFC (Request for Comments) process
+* Need approval from majority of maintainers
+* Must include migration guide
+
+=== Code of Conduct
+
+All participants are expected to follow our Code of Conduct. Violations
+can be reported to the maintainers.
+
+=== Communication
+
+* *Issues*: For bug reports and feature requests
+* *Discussions*: For questions and general discussion
+* *Pull Requests*: For code contributions
+
+=== Licensing
+
+All contributions are made under the terms of the repository’s LICENSE
+file. By submitting a pull request, you agree to license your
+contributions accordingly.
+
+'''''
+
+_Last updated: 2026-07-18_

SECURITY.adoc

@@ -0,0 +1,11 @@
+== Security Policy
+
+=== Reporting a Vulnerability
+
+*Email:* j.d.a.jewell@open.ac.uk
+
+*Response timeline:* - Acknowledgement within 48 hours - Initial
+assessment within 7 days - Fix or mitigation within 90 days
+
+*Safe harbour:* We will not pursue legal action against security
+researchers who follow responsible disclosure.

mvt/README.adoc

@@ -0,0 +1,42 @@
+== Econosphere MVT 0.0: Public Goods Kernel
+
+Rollback prototype for testing only the core public-goods dilemma:
+
+[source,text]
+----
+private growth -> shared stress -> pledge -> defection/cooperation -> collapse or survival
+----
+
+This directory is intentionally self-contained and dependency-free. The
+active ruleset is `+mvt-public-goods-kernel+` in `+src/kernel+`. The
+larger Alpha 0.1 engine remains in `+src/engine+` for later reuse, but
+the UI now runs the simplified thesis test.
+
+=== Run
+
+[source,sh]
+----
+cd mvt
+deno task test
+deno task serve
+----
+
+Then open `+http://localhost:5173/+`.
+
+=== Scope
+
+Implemented:
+
+* 4 asymmetric roles
+* 5-turn deterministic state machine
+* One private value: Prosperity
+* One shared danger track: System Stress
+* One pledge type: Stewardship Pledge
+* Three actions: Develop, Steward, Hedge
+* Deterministic crisis bands and highest-contributor penalty
+* Save/load/export as JSON through local browser controls
+* Event log, stress history, turn history, collapse gate, endgame
+explanation
+
+The active kernel can be imported independently from
+`+src/kernel/index.js+`.