Build the Darwin v50 evidence-first cognitive architecture laboratory

.editorconfig

@@ -0,0 +1,18 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.py]
+indent_style = space
+indent_size = 4
+
+[*.{md,json,yml,yaml,toml}]
+indent_style = space
+indent_size = 2
+
+[*.bat]
+end_of_line = crlf

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,23 @@
+## What changed
+
+Describe the code, protocol, or documentation change in plain language.
+
+## Why
+
+State the problem or falsifiable question this change addresses.
+
+## Validation
+
+List the exact commands and observed results.
+
+## Evidence boundary
+
+Explain what the change supports and what remains unsupported.
+
+## Checklist
+
+- [ ] Final seeds were not used during development.
+- [ ] New claims have registered baselines and thresholds.
+- [ ] Failed criteria remain visible.
+- [ ] Runtime databases, logs, exports, and credentials are not included.
+- [ ] Maintained documentation is written in direct English.

.github/workflows/ci.yml

@@ -0,0 +1,31 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: windows-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: pip
+
+      - name: Install package
+        run: python -m pip install -e .
+
+      - name: Check maintained repository surface
+        run: python scripts/check_maintained_surface.py
+
+      - name: Run test suite
+        env:
+          PYTHONPATH: src
+        run: python -m unittest discover -s tests -v

.gitignore

@@ -16,15 +16,14 @@ Thumbs.db
 baselines/
 v47_patch_backups/
 v48_patch_backups/
-darwin_home/backups/
-darwin_home/logs/
-darwin_home/snapshots/
-darwin_home/music_cache_v49_16/
 
-# SQLite transient files. The current Darwin memory DB is intentionally kept.
-darwin_home/*.db-journal
-darwin_home/*.db-shm
-darwin_home/*.db-wal
-darwin_home/*.sqlite-journal
-darwin_home/*.sqlite-shm
-darwin_home/*.sqlite-wal
+# Darwin runtime state belongs to the local machine, not to source control.
+darwin_home/*
+!darwin_home/config.example.json
+
+# Build artifacts.
+build/
+dist/
+*.egg-info/
+.coverage
+htmlcov/

Abrir_Darwin_Acordar_Com_Voz.bat

@@ -25,6 +25,12 @@ if %errorlevel%==0 (
     exit /b
 )
 
+set "DARWIN_CODEX_PYTHONW=%USERPROFILE%\.cache\codex-runtimes\codex-primary-runtime\dependencies\python\pythonw.exe"
+if exist "%DARWIN_CODEX_PYTHONW%" (
+    start "" "%DARWIN_CODEX_PYTHONW%" darwin_wake_word_guardian_v49_34.py
+    exit /b
+)
+
 echo Nao encontrei Python no PATH.
-echo Abra pelo Codex com: py darwin_wake_word_guardian_v49_34.py
+echo Tambem nao encontrei o runtime Python fornecido pelo Codex.
 pause

CONTRIBUTING.md

@@ -0,0 +1,70 @@
+# Contributing to Darwin
+
+Darwin is easier to improve when claims stay smaller than the code that supports
+them. A useful contribution makes the evidence clearer, the failure mode harder
+to hide, or the architecture easier to test.
+
+## Development setup
+
+```powershell
+py -m pip install -e .
+$env:PYTHONPATH = "src"
+py -m unittest discover -s tests -v
+```
+
+Python 3.11 or newer is required.
+
+## Where new work belongs
+
+- package code: `src/darwin_v50`
+- tests: `tests`
+- experiment records: `docs/v50`
+- architecture and maintenance guides: `docs`
+
+Do not add another versioned Python program to the repository root. Root-level
+v47-v49 files are a compatibility surface and will be migrated separately.
+
+## Experiment checklist
+
+Before running final seeds, write down:
+
+- the exact capability claim;
+- development, calibration, and final seed families;
+- what information the agent can observe;
+- baselines and ablations;
+- metrics and conjunctive thresholds;
+- tie-breaking and selection rules;
+- snapshot and causal-order invariants;
+- conditions that refute the hypothesis;
+- the strongest evidence level the evaluator can support.
+
+After the final run, record every metric and every failed criterion. Do not tune
+against final seeds and then present the same seeds as held out.
+
+## Writing style
+
+Use direct, ordinary English. Avoid promotional claims, synthetic enthusiasm,
+and vague phrases such as “revolutionary intelligence” or “human-like
+understanding.” Prefer a concrete sentence:
+
+> The planner solved 96 of 100 registered tasks.
+
+over an interpretation the experiment did not test:
+
+> Darwin now understands the world.
+
+State limitations close to the result they qualify. A failed hypothesis is a
+valid result and should remain visible.
+
+## Pull requests
+
+A pull request should explain:
+
+- what changed;
+- why the change was needed;
+- which claim or invariant it affects;
+- how it was tested;
+- what remains unsupported.
+
+Keep runtime databases, logs, exports, credentials, and local snapshots out of
+Git.