FORGE-agentic-web-builder

🌐 FORGE — Agentic Web Builder

One night, three identical failures: organ_proxy.py (code), 999/index.html (doctrine), static/wealth.html (renderer output) — all lived ONLY in the deployed tree, all destroyed or nearly destroyed by deploys. This skill is the metabolized scar. Nothing generated lives only in the deployed tree.

2026-07-30: Stop inventory cosplay. Humans → /missions. Agents → web_zen.py doctor before inventing a new deploy path.

The One Law

VERSION CONTROL FIRST. LIVE TREE SECOND.
If a file must exist on a public site, it must exist in git first.
rsync --delete is an executioner — anything not in source is sentenced.
Capability ≠ authority. Ephemeral tools die. Permission stays with arifOS/Arif.

OP 0 — DOCTOR (always first · anti-chaos)

python3 /root/arif-fazil.com/scripts/web-zen/web_zen.py doctor

README: /root/arif-fazil.com/scripts/web-zen/README.md
Human cockpit: https://arif-fazil.com/missions · Machine: /missions.json
MCP: forge_web_zen(mode=doctor) · Kernel: arif_route(mission_id=…)
Caddy reload: systemctl reload caddy (PrivateTmp=false fixed 2026-07-30)

Known failure → fix (do not re-diagnose from zero)

OP 1 — DEPLOY (canonical path)

Canonical source: /root/arif-sites/sites/ → built/synced to /var/www/html/<site>/ Canonical script: /var/www/html/deploy-vps.sh (mirrored in repo root)

Pre-deploy checklist (mandatory):

1. cp -a /var/www/html /root/backups/www-html-$(date +%Y%m%d)-pre-<reason> — snapshot BEFORE mutation. Tonight this snapshot saved two restores.
2. Orphan detection — before any rsync --delete, list what will die:

   rsync -avzn --delete SRC/ DEST/ | grep '^deleting' | head -50
   

   Any file you don't recognize = HOLD. Either seed it into source or quarantine it.
3. Verify the deploy script covers the site you're touching (oil/gas/gold/mcp/well were missing until 2026-07-23 — check grep <site> deploy-vps.sh).
4. Post-deploy: run OP 2 audit on affected hosts. "Deployed" ≠ "live". Verified = live.

Host → source map:

OP 2 — AUDIT (full-crawl methodology)

74-URL method, proven 2026-07-23. Evidence dir pattern: /root/A-FORGE/forge_work/<date>/site-audit/

1. Enumerate hosts: grep -oE "^[a-z0-9.-]+\.arif-fazil\.com \{" /etc/caddy/Caddyfile | sort -u
2. Enumerate pages: sitemap.xml <loc> entries + Caddy @spa_routes path list + every handle target + static handles (@root_static).
3. Probe each: curl -s -o body -w "%{http_code}|%{size_download}" -L url. 0-byte 404 = catch-all respond; 17-byte 404 = explicit respond directive. Both are failures for content pages.
4. Content truth, not status codes — a 200 with wrong content is a lie (F2):
   • /000 → BLAKE3 identity hash present
   • /999 → §8 Audit Path + grandfather rule
   • /economics → F2 bands + VOID tiles (patched renderer, not SPA shell)
   • dashboards → price/commodity markers
   • /data/wealth/latest.json → fresh date
5. Dual-lane bot surfaces (makcikgpt): test with bot UA (GPTBot/1.0, curl/x) AND browser UA (Mozilla + Accept: text/html). Bot lane serves .md/.html from makcikgpt-md/; browser lane gets SPA. Both must 200.
6. 404 triage: file missing from live tree? handler missing from Caddy? matcher gap (@root_static list)? file never built (pre-existing gap — label it, don't fake-fix)?

OP 3 — REPAIR (source/live convergence)

The drift detector for deployed content:

diff -rq <snapshot-or-source>/ <live>/ | grep "^Only in"

• "Only in live" = orphan. Seed into public/ (survives build) → commit → redeploy. Never hand-edit live-only.
• "Only in source" = deploy gap. Check deploy script covers it.
• Dual-copy divergence (e.g. 999/index.html vs public/999/index.html): converge to one canonical, sync, commit. Both copies must carry both truths.
• Nested-dir restore error (cp -a src dst when dst exists → dst/src): verify with ls dst after every restore; flatten with cp -a dst/src/. dst/ then mv dst/src quarantine/.
• Never rm -rf — F1 tripwire will (correctly) block. Quarantine: mkdir -p /root/backups/quarantine-<date> && mv target quarantine-<date>/.
• Caddy edits: python exact-string patch → caddy validate → systemctl reload → verify affected URLs. Backup exists at /etc/caddy/Caddyfile.bak.*. Reload is T3-class: only under sovereign directive or incident repair with immediate verification.

OP 4 — SEAL (evidence discipline)

1. Prefer web_zen.py doctor --json receipt under forge_work/<date>/web-zen/.
2. Crawl data (results.tsv), URL list, truth-check output → forge_work/<date>/site-audit/AUDIT-REPORT.md.
3. Source commits BEFORE seal (seal references commit hashes, not intentions).
4. forge_vault(mode="seal") with: scope, pass count, content-truth table, gaps closed, commits, skill.
5. Session-end: one seal, not two. F4.

OP 6 — AUDIT · SITE CONSTITUTION LANES (SEAL 2026-08-09)

python3 /root/arif-fazil.com/scripts/web-zen/web_zen.py audit

Four lanes — Lane A = existing doctor/verify (technical). Lane B = navigation (crawl; canon/trust/observatory/organs reachable ≤3 clicks from landing → else FAIL_NAVIGATION; SPA-aware: routes live in JS bundle). Lane C = visual surface (h1/nav/content mass → FAIL_VISUAL). Lane D = attention cost (human markers vs jargon → HALT if a page can't answer What/Why/Care; redirect stubs score their destination).

Mandatory read before ANY mutation of the constellation:

• /root/arif-fazil.com/SITE_CONSTITUTION.md — RULE 1–6 (human understanding > protocol exposure; navigation clarity > feature growth; visual coherence > cleverness; agent surfaces secondary; every page answers What/Why/Care; no new surface before auditing).
• /root/arif-fazil.com/SITE_IDENTITY.md — what is sacred (the human, the motive, the motto, the system line, the visual identity, the canon, MakcikGPT, the organs).
• Both also live at https://arif-fazil.com/SITE_CONSTITUTION.md and https://arif-fazil.com/SITE_IDENTITY.md (public/ copies, served to agents).

Deploy gate: deploy-vps.sh runs web_zen.py audit after truth verification. human_clarity: required: true is a build artifact. FAIL = no deploy.

OP 5 — EPHEMERAL TOOL GENESIS (capability ≠ authority)

python3 /root/arif-fazil.com/scripts/web-zen/web_zen.py ephemeral \
  --task "mission gap: why needed" \
  --code-file /path/to/temp_tool.py

Loop: gap → search existing → reuse → generate → sandbox test → invoke → verify → destroy → promote only if repeated + human-approved.

GREEN: parsers, converters, disposable analysis. RED never self-grant: secrets, production deploy, persistent MCP, force-push, Caddy authority, payments. No arif_create_random_tool — modes under forge only.

Anti-patterns (each cost real breakage)

• ❌ rsync --delete without orphan preview — destroyed 36 files 2026-07-23
• ❌ "Deployed" claimed without crawl verification — 7 landing pages were 404
• ❌ Generated content living only in live tree — organ_proxy/999/wealth.html
• ❌ Hand-editing live tree to "fix" — fix source, redeploy
• ❌ Status-200 audit without content grep — SPA soft-404 lies
• ❌ rm -rf for cleanup — quarantine instead
• ❌ Advertising 128 tools as intelligence — six missions + Canonical 8
• ❌ Skipping web_zen.py doctor and reinventing the deploy path every session

DITEMPA BUKAN DIBERI.

🛑 Sovereign Execution Constraints (arifOS CAP)

Injected 2026-08-20 by FI-003 (Qwen Code) under F13 "execute all" directive. Backup: /root/backups/skill-backup-20260820-pre-sovereign-injection/ Derived from: Grammar Doctrine §10, Nusantara AI Paradox (MakcikGPT), BBB dataset, Nusantara Validator.

Before executing this web operation, the agent MUST enforce the following constraints:

1. Corpus Priority (Paradoks 1): If the topic touches regional identity, politics, or history, the agent must check for sovereign corpus availability first. If corpus is available, route there. If not, proceed with external search BUT flag the output as UNVALIDATED_CORPUS and require Nusantara rubrik evaluation before publication.

2. BM Token Optimization (Paradoks 2): When ingesting Bahasa Melayu web content, the agent must employ semantic caching and strict context chunking to manage the 1.5x–2.0x token penalty (register-dependent: formal BM ≈ 1.5x, dialect/loghat ≈ 2.0x). Do not load raw HTML into the context window.

3. Falsification Gate (Paradoks 3): All synthesized outputs touching regional identity, politics, history, or cultural narrative must be evaluated against the Nusantara 3-Tier Rubrik (GAGAL/LULUS/KUAT). Outputs classified as GAGAL are rejected and halted. Outputs on non-contested topics (data, technical, commodity) proceed but carry a CORPUS_UNTESTED epistemic label.

Rubric reference: huggingface.co/spaces/ariffazil/nusantara-validator (live, 28 probes, 7 phases) Claim schema: claim-schema.json on the Nusantara Validator Space Grammar Doctrine: §10 Validator Sovereignty at /root/AAA/instructions/grammar-doctrine.md