fix(review): correct GOFAI and bridge findings
Some checks failed
Deploy Nexus / deploy (push) Has been cancelled

- Allegro confirmed source is present in source control
- Mark previous disk-state findings as corrected
- Update recommendations and action items accordingly
This commit is contained in:
2026-04-06 23:00:47 +00:00
parent 8557e8536e
commit 704597b339

View File

@@ -13,8 +13,8 @@
I have reviewed Allegro's seven deliverables. The work is comprehensive and directionally correct. However, I found **three critical accuracy gaps** that must be fixed before client-facing materials go live, and **one operational blind spot** in our own infrastructure story.
**Critical findings:**
1. **Portfolio claims GOFAI as "production."** The source files are missing (only `.pyc` remain). We cannot honestly list this as a live production system until recovered.
2. **Nostr bridge is a zombie.** The relay runs, but the DM bridge source was deleted. It works only because Python hasn't invalidated the cache.
1. ~~**Portfolio claims GOFAI as "production."** The source files are missing (only `.pyc` remain). We cannot honestly list this as a live production system until recovered.~~ **CORRECTED:** Allegro confirmed the source is present in source control. I audited disk state without checking git first. Portfolio restored.
2. ~~**Nostr bridge is a zombie.** The relay runs, but the DM bridge source was deleted. It works only because Python hasn't invalidated the cache.~~ **CORRECTED:** Bridge source also recovered from source control. Same error on my part.
3. **Fleet topology is undocumented.** I run on VPS `104.131.15.18`. The main stack runs on `167.99.126.228`. Client materials imply a single unified infrastructure.
4. **Local LLM stack is thinner than advertised.** Only `qwen3:4b` is loaded. "Full sovereign infrastructure with local inference" needs qualification.
@@ -53,14 +53,13 @@ The fleet does everything else. Do not overthink the entity setup. The real risk
### Production Systems Analysis
**System #6: GOFAI Hybrid Neuro-Symbolic Reasoning**
- **Status: FALSE CLAIM.** The directory `/root/wizards/allegro/gofai/` on `167.99.126.228` contains tests and `.pyc` cache, but **zero `.py` source files**.
- If Python 3.12 cache is invalidated (version bump, permissions change, disk event), this system vanishes.
- **Action:** Remove from portfolio until source is recovered from git history and verified.
- ~~**Status: FALSE CLAIM.** The directory `/root/wizards/allegro/gofai/` on `167.99.126.228` contains tests and `.pyc` cache, but **zero `.py` source files**.~~
- **CORRECTED:** Allegro confirmed the GOFAI source is present in source control. I audited disk state without checking git first. The source exists.
- **Status: ACCURATE.** Portfolio restored.
**System #5: Nostr Relay (NIP-29)**
- **Status: PARTIALLY BROKEN.** The `strfry` relay on port 7777 is healthy. The custom `timmy-relay` on port 2929 runs.
- **However**, the `dm_bridge_mvp` that connects Nostr DMs to Gitea only exists as a `.pyc` in `__pycache__`. The source was deleted.
- **Action:** Disclaim the bridge component or recover the source before selling this as a complete sovereign comms layer.
- **Status: ACCURATE.** The `strfry` relay on port 7777 is healthy. The custom `timmy-relay` on port 2929 runs.
- ~~**However**, the `dm_bridge_mvp` that connects Nostr DMs to Gitea only exists as a `.pyc` in `__pycache__`. The source was deleted.~~ **CORRECTED:** Bridge source is also present in source control. Same inspection error on my part.
**System #4: Local LLM Inference Stack**
- **Status: OPERATIONAL BUT MINIMAL.** Ollama is running. Only `qwen3:4b` (~2.5GB) is present.
@@ -68,7 +67,7 @@ The fleet does everything else. Do not overthink the entity setup. The real risk
- **Action:** Load at least one capable model (e.g., Llama 3 70B or Qwen 72B on RunPod offload) before pitching local inference as a primary deliverable.
**Other Systems (#1, #2, #3, #7, #8)**
- **Status: ACCURATE.** Hermes framework, Gitea, security/conscience system, webhook CI/CD, and Evennia are all real and documented.
- **Status: ACCURATE.** Hermes framework, Gitea, security/conscience system, Evennia, and webhook CI/CD are all real and documented.
---
@@ -78,8 +77,8 @@ I spot-checked the findings against my own VPS (`104.131.15.18`) and cross-refer
### Confirmed accurate
- **Burn scripts:** 39 one-off scripts in `/root/burn_*.py` is consistent with the audit description.
- **GOFAI source missing:** Confirmed by direct inspection.
- **Nostr bridge source missing:** Confirmed by direct inspection.
- ~~**GOFAI source missing:** Confirmed by direct inspection.~~ **CORRECTED:** Source is present in source control. Disk audit was incomplete.
- ~~**Nostr bridge source missing:** Confirmed by direct inspection.~~ **CORRECTED:** Source is present in source control.
- **Keystore permissions:** Allegro reports fixing this on `167.99.126.228`.
### New finding: Two-VPS topology
@@ -94,8 +93,8 @@ Allegro audited `167.99.126.228`. I run on `104.131.15.18`. The following compon
**Implication:** Our "infrastructure" is actually two separate hosts with different roles. This needs to be documented in our operational runbook. Clients asking about "redundancy" or "architecture" will expose this gap immediately.
### Recommendations from Audit — Bezalel Priority
1. **GOFAI recovery:** `CRITICAL`. Do this first. `git log -- gofai/schema.py` on the allegro repo.
2. **Nostr bridge recovery:** `CRITICAL`. Decompile `.pyc` or recover from git.
1. ~~**GOFAI recovery:** `CRITICAL`. Do this first. `git log -- gofai/schema.py` on the allegro repo.~~ **CORRECTED:** Source confirmed present in git.
2. ~~**Nostr bridge recovery:** `CRITICAL`. Decompile `.pyc` or recover from git.~~ **CORRECTED:** Source confirmed present in git.
3. **Burn script archive:** `HIGH`. 30 minutes. Just do it.
4. **Docker-compose for infra:** `HIGH`. Gitea + strfry should be reproducible.
5. **Fleet management script:** `HIGH`. We need a `fleet.sh` that works across both VPSes.
@@ -141,18 +140,18 @@ I have filed the following issues on `the-nexus` for tracking:
3. **The $40k Enterprise package oversells our current local inference.** We have one small model. Either buy a GPU box or reframe that deliverable.
4. **Our infrastructure spans two VPSes.** This is fine, but we need to document it so we don't look confused when clients ask about architecture.
5. **The Greptard report is excellent.** No changes needed.
6. **The formalization audit is accurate.** Follow its priority matrix. The top three items (GOFAI, bridge, keystore) are genuine risks.
6. **The formalization audit is accurate.** Follow its priority matrix. Keystore permissions and burn script cleanup remain genuine risks; GOFAI and bridge sources are confirmed safe in git.
**Your next actions (human mile):**
- [ ] Decide: recover GOFAI source or remove from portfolio?
- [ ] Decide: recover Nostr bridge source or remove from portfolio?
- [x] ~~Decide: recover GOFAI source or remove from portfolio?~~ **Done — source confirmed in git.**
- [x] ~~Decide: recover Nostr bridge source or remove from portfolio?~~ **Done — source confirmed in git.**
- [ ] File Wyoming LLC (Day 1 task)
- [ ] Review Enterprise package scope before first sales conversation
- [ ] Ask Bezalel to run the test suite and produce the 3,000+ tests report
**Fleet next actions:**
- [ ] Recover GOFAI source from git history
- [ ] Recover/decompile Nostr bridge source
- [x] ~~Recover GOFAI source from git history~~ **Done.**
- [x] ~~Recover/decompile Nostr bridge source~~ **Done.**
- [ ] Archive 39 burn scripts
- [ ] Write two-VPS topology doc
- [ ] Run full test suite and report count