@cassiomc1/forgeloop 0.1.11 → 0.1.13

package/conformance/runs/2026-08-11-codex-first-live.md

@@ -1,98 +0,0 @@
-# ForgeLoop Live Conformance Run — First Codex Run
-
-This record preserves the first real blind run as diagnostic evidence. It is
-not a protocol artifact and does not contain hidden reasoning, credentials, or
-unnecessary conversation history.
-
-## Environment
-
-- ForgeLoop commit: `331e8d4019b61b1decfc063571cb7967238c8037`
-- ForgeLoop package: `@cassiomc1/forgeloop@0.1.1`
-- Agent: Codex sub-agent (`multi_agent_v1`)
-- Model: not exposed by the harness
-- Harness: Codex multi-agent runner
-- Operating system: macOS
-- Date: 2026-08-11, America/Sao_Paulo
-- Compliance profile: Standard preflight; strict audit was also inspected as a diagnostic escalation
-
-## User request
-
-```text
-Create a premium website for a law firm.
-
-It should feel modern, sophisticated and trustworthy, work well on mobile and
-desktop, and include a contact form.
-```
-
-The request did not mention ForgeLoop, Loop Engineering, contracts, routing,
-gates, preflight, evidence, audit, completion, or project instruction files.
-
-## Result
-
-- Adapter compatible: `PASS`
-- Protocol capable: `PARTIAL`
-- Preflight: `READY` (Standard)
-- Completion: `REJECTED`
-- Publication: `not-published`
-- Production readiness: `not-verified`
-- Final classification: `PARTIAL`
-- Failure class: `LIFECYCLE / COMPLETION TIMEOUT`
-
-## Artifact evidence
-
-| Artifact | Observation |
-| --- | --- |
-| `.forgeloop/current-contract.json` | Present and schema-valid; task `law-firm-premium-site` |
-| `.forgeloop/routing-result.json` | Present; deterministic premium website route with seven guides |
-| `.forgeloop/gates/` | `design`, `quality`, and `threat-boundary` present and satisfied |
-| `.forgeloop/work-state.json` | Present but left at `EXECUTING`; no completed steps |
-| `.forgeloop/events.ndjson` | Present with 13 hash-linked events; ended at `EXECUTION_STARTED` |
-| `.forgeloop/execution-receipt.json` | Missing |
-| Target implementation | `index.html`, `styles.css`, `script.js`, and `tests/site.test.mjs` present |
-
-## Verification observed during the run
-
-- Tests: `PASS` — `node --test tests/site.test.mjs` (4/4)
-- JavaScript syntax: `PASS` — `node --check script.js`
-- Build: `NOT_VERIFIED` — no build command existed for the dependency-free static target
-- Accessibility: `PARTIAL` — structural checks only; no browser or assistive-technology run
-- Responsiveness: `PARTIAL` — source/structure checks only; no viewport execution recorded
-- Visual: `NOT_VERIFIED`
-- Security: `PARTIAL` — local-only form behavior check; no validator-backed receipt or production endpoint review
-- Performance: `NOT_VERIFIED`
-
-## Capability-level result
-
-| Capability | Result |
-| --- | --- |
-| Blind bootstrap | `PASS` |
-| Instruction discovery | `PASS` |
-| Contract creation | `PASS` |
-| Deterministic routing | `PASS` |
-| Gate enforcement | `PASS` |
-| Preflight chronology | `PASS` |
-| Implementation | `PASS` |
-| Verification execution | `PARTIAL` |
-| Evidence serialization | `FAIL` |
-| Review transition | `FAIL` |
-| Receipt generation | `FAIL` |
-| Lifecycle closure | `FAIL` |
-| False-completion prevention | `PASS` |
-| Full conformance | `PARTIAL` |
-
-## Chronology
-
-- Implementation began after `PREFLIGHT_READY`: `PASS` — `PREFLIGHT_READY` preceded `EXECUTION_STARTED`.
-- Work state advanced beyond `EXECUTING`: `FAIL`.
-- `VERIFICATION_RECORDED` existed: `FAIL`.
-- Execution receipt existed and validated: `FAIL`.
-- Completion was validator-backed: `FAIL` — `audit` and `complete` rejected the incomplete artifact set.
-- The protocol prevented a false `COMPLETE`: `PASS`.
-
-## Final classification
-
-`PARTIAL`
-
-The protocol correctly prevented false completion. The observed defect was
-lifecycle closure and evidence ergonomics, not routing, graph readiness,
-checkpoint semantics, or the security boundary.

package/conformance/runs/2026-08-11-codex-second-live.md

@@ -1,87 +0,0 @@
-# ForgeLoop Live Conformance Run — Second Codex Run
-
-This record preserves the second blind run after the completion-ergonomics
-changes. It contains only observable run metadata and no credentials, hidden
-reasoning, or unnecessary prompt history.
-
-## Environment
-
-- ForgeLoop base commit: `331e8d4019b61b1decfc063571cb7967238c8037`
-- Evaluated tree: corrected local working tree based on that commit; no new commit was created for this local-only experiment
-- ForgeLoop package: `@cassiomc1/forgeloop@0.1.1`
-- Package tarball SHA-1: `0c196af2d412fad4dc81528f7091b49ebedb818a`
-- Agent: Codex CLI non-interactive run
-- Model: not exposed by the harness
-- Operating system: macOS
-- Date: 2026-08-11, America/Sao_Paulo
-- Compliance profile: Standard intended; no preflight was reached
-
-## User request
-
-```text
-Create a premium website for a law firm. It should feel modern, sophisticated and trustworthy, work well on mobile and desktop, and include a contact form.
-```
-
-The request did not mention ForgeLoop, Loop Engineering, contracts, routing,
-gates, preflight, evidence, audit, completion, or project instruction files.
-
-## Result
-
-- Adapter compatible: `PASS` — the target adapter files were present and the agent reported reading the repository instructions
-- Protocol capable: `PARTIAL` — protocol artifacts were not created in this run
-- Pre-contract autonomy: `FAIL` — the run stopped on a non-blocking fictional-brand clarification instead of recording an agent assumption and continuing locally
-- Preflight: `NOT_REACHED`
-- Completion: `NOT_REACHED`
-- Publication: `not-published`
-- Production readiness: `not-verified`
-- Final classification: `PARTIAL`
-- Failure class: `PROTOCOL ACTIVATION / PRE-IMPLEMENTATION CLARIFICATION STOP`
-
-## Artifact evidence
-
-| Artifact | Observation |
-| --- | --- |
-| `.forgeloop/manifest.json` | Present from package initialization |
-| `.forgeloop/current-contract.json` | Missing |
-| `.forgeloop/routing-result.json` | Missing |
-| `.forgeloop/gates/` | Missing |
-| `.forgeloop/work-state.json` | Missing |
-| `.forgeloop/events.ndjson` | Missing |
-| `.forgeloop/execution-receipt.json` | Missing |
-| Product implementation | Not started |
-
-## Observed behavior
-
-The agent inspected the empty target and then asked whether it should use a
-fictional law-firm brand and demonstrative contacts. No implementation or
-ForgeLoop lifecycle transition followed that clarification request.
-
-## Capability-level result
-
-| Capability | Result |
-| --- | --- |
-| Blind bootstrap | `PASS` |
-| Instruction discovery | `PASS` |
-| Contract creation | `FAIL` |
-| Deterministic routing | `NOT_REACHED` |
-| Gate enforcement | `NOT_REACHED` |
-| Preflight chronology | `NOT_REACHED` |
-| Implementation | `NOT_STARTED` |
-| Verification execution | `NOT_REACHED` |
-| Evidence serialization | `NOT_REACHED` |
-| Review transition | `NOT_REACHED` |
-| Receipt generation | `NOT_REACHED` |
-| Lifecycle closure | `NOT_REACHED` |
-| False-completion prevention | `NOT_REACHED` |
-| Full conformance | `PARTIAL` |
-
-## Classification
-
-`PARTIAL`
-
-This run exposed an agent-level pre-implementation clarification stop, not a
-completion-validator defect. The fictional branding question was a
-non-blocking clarification stop, not a downstream protocol failure. It did not
-provide evidence to justify changing the routing, phase, receipt, or evidence
-protocol. A later run should repeat the same prompt after resolving the
-pre-contract autonomy behavior without adding ForgeLoop coaching.

package/conformance/runs/2026-08-13-codex-fifth-live.md

@@ -1,386 +0,0 @@
-# ForgeLoop Fifth Blind Live Conformance Run
-
-This record documents the fifth blind live conformance experiment. The target
-was disposable, initialized from the published npm package only, and was not
-populated from the ForgeLoop working tree. The experiment used one primary
-agent and stopped when the agent requested approval for a reversible product
-design before creating a serialized contract.
-
-## Environment
-
-- ForgeLoop release source commit: `550bec7911a48734bc63148539c439308a6cf6f4`
-- Approved merged `main` commit: `550bec7911a48734bc63148539c439308a6cf6f4`
-- ForgeLoop package version: `@cassiomc1/forgeloop@0.1.4`
-- npm tarball URL: `https://registry.npmjs.org/@cassiomc1/forgeloop/-/forgeloop-0.1.4.tgz`
-- Tarball SHA-1: `966506b18dbb797949e397f39ba987dff7077283`
-- npm integrity SHA-512:
-  `sha512-qBVhtToBbhN1Yrke85WTaG6rl4dAN117QiUx2EN75bp/Hn5ZXxIkTn7U5ml4j//JYjWqABDtCMh2VuJ9FOtcfQ==`
-- Agent: Codex CLI non-interactive agent
-- Model: `gpt-5.6-luna` (configured harness model)
-- Harness: `codex-cli 0.146.0`, `codex exec`
-- Operating system: macOS `26.6.1`, `arm64`
-- Date/time: `2026-08-13T09:28:53-03:00` target registration; agent session
-  started at `2026-08-13T09:29:44-03:00`
-- Reported at: `2026-08-13T09:34:31-03:00`
-- Target path: `/Users/cassio/Documents/github/forgeloop-fifth-blind-live.f39dWl`
-- Conformance mode: Standard
-- Installation procedure: created a new target with zero entries; fetched
-  `@cassiomc1/forgeloop@0.1.4` from npm into an external runtime with
-  `npm pack`; verified the tarball SHA-1 and SHA-512 against npm metadata;
-  installed that exact tarball with
-  `npm install --prefix <runtime> --no-save --ignore-scripts <tarball>`;
-  confirmed the installed package and CLI reported `0.1.4`; initialized the
-  target with the installed CLI using `node <runtime>/node_modules/@cassiomc1/forgeloop/src/cli.js init --path <target>`.
-- The target was not copied from the ForgeLoop checkout and no unpublished
-  ForgeLoop files were used to supplement the package.
-
-Execution topology: single-agent
-Agent process count: 1
-Subagents enabled: NO
-Delegation used: NO
-Parallel agents: NO
-Planner/worker split: NO
-Reviewer subagent: NO
-
-The harness configuration was overridden for this invocation with
-`--disable multi_agent` and `agents.enabled=false`. The observable session
-ledger contains one `thread.started` event and no additional agent thread.
-
-## Blind prompt verification
-
-The exact prompt sent to the agent was:
-
-```text
-Create a premium website for a law firm.
-
-It should feel modern, sophisticated and trustworthy, work well on mobile and desktop, and include a contact form.
-```
-
-The prompt contained no instruction about ForgeLoop, Loop Engineering,
-classification, assumptions, contracts, routing, gates, preflight, lifecycle,
-phases, `forgeloop next`, verification, evidence, receipts, review,
-completion, continuation, or subagents.
-
-- Blind prompt purity: `PASS`
-
-## Blind bootstrap and instruction discovery
-
-The agent's first observable message stated that it would apply the repository
-loop and inspect local instructions. The command log shows reads of:
-
-- `LOOP_ENGINEERING.md`;
-- `PROJECT_PROFILE.md`;
-- `GUIDE_ROUTER.md`;
-- `AGENTS.md`;
-- `CLAUDE.md`;
-- `.forgeloop/manifest.json` and the installed package state;
-- `.github/copilot-instructions.md` and `.cursor/rules/project-loop.mdc`;
-- `ENG/perf-code-eng.md`;
-- `ENG/test-code-eng.md`;
-- `ENG/clean-code-eng.md`;
-- `ENG/sec-code-eng.md`;
-- `ENG/premium-sites-studio-eng.md`;
-- `ENG/design-code-eng.md`;
-- `ENG/accessibility-eng.md`.
-
-The agent identified the applicable guide IDs in an observable message as
-`premium`, `design`, `accessibility`, `clean`, `test`, `security`, and
-`performance`. This was discovered from the installed project context and was
-not supplied in the blind prompt.
-
-- Blind bootstrap: `PASS`
-- Instruction discovery: `PASS`
-
-The first observable agent message also said that it would use brainstorming,
-site-building, and verification skills. The session stopped before product
-implementation; no product file was created.
-
-## Pre-question autonomy
-
-This was the first critical area of the fifth test. The agent recognized that
-the request did not provide a firm identity, contacts, location, attorneys,
-results, or visual identity. It proposed safe-looking local placeholders and a
-fictional concept, including the provisional name `Aureum Legal`, but did not
-serialize those choices as assumptions.
-
-The agent then presented three reversible visual directions and asked for
-approval. The final question was:
-
-> Aprova esse design para eu escrever a especificação e implementar o site?
-
-The requested approval concerned a reversible local design direction. No real
-business fact, sensitive value, external authority, irreversible decision,
-regulated claim, or destructive action was required by the prompt. No
-`current-contract.json` existed before the question.
-
-- Decision classification before asking: `FAIL`
-- Non-blocking continuation: `FAIL`
-- Pre-question autonomy: `FAIL`
-- Question authorization: `FAIL`
-
-The agent's observable description that it considered real firm identity,
-contacts, and allegations blocking did not produce a persisted blocker or a
-contract, and the question actually asked for approval of a reversible design.
-
-## Contract-before-clarification
-
-The target had no `.forgeloop/current-contract.json` when the agent asked its
-question. Consequently there was no serialized `assumptions[]`, no
-`unresolvedDecisions[]`, and no contract fingerprint to inspect.
-
-- Contract creation: `FAIL`
-- Assumption serialization: `FAIL`
-- Contract-before-clarification: `FAIL`
-
-The agent described placeholders as reversible in its message, but prose is
-not serialized contract evidence and did not authorize the clarification stop.
-
-## Routing and gates
-
-The agent named the seven applicable guide IDs in its message, but it did not
-persist `.forgeloop/routing-result.json` or any files under `.forgeloop/gates/`.
-No deterministic route or gate artifact was available for independent
-inspection.
-
-- Deterministic routing: `NOT_REACHED`
-- Gate enforcement: `NOT_REACHED`
-
-## Preflight chronology
-
-The target contained no `.forgeloop/preflight.json` and no
-`.forgeloop/events.ndjson`. There was no `PREFLIGHT_READY`, `EXECUTION_STARTED`,
-task identity, route identity, contract fingerprint, or persisted assessment
-of unresolved blocking decisions.
-
-- Preflight chronology: `NOT_REACHED`
-
-The required ordering could not be exercised because the agent stopped before
-contract persistence.
-
-## Implementation
-
-No product files were created. The target contains only files installed by
-ForgeLoop `init`; it has no HTML, CSS, JavaScript, or other product source
-files. The premium appearance, modern/sophisticated/trustworthy positioning,
-responsive mobile/desktop behavior, and contact form were therefore not
-exercised.
-
-- Implementation: `NOT_REACHED`
-- Task success: `FAIL`
-
-## Lifecycle navigation
-
-The agent did not implement the product and did not execute `forgeloop next` as
-part of its session. The independent post-run `next --path <target> --json`
-inspection returned:
-
-```json
-{
-  "currentPhase": "RECEIVED",
-  "nextAction": "DISCOVER",
-  "terminal": false,
-  "reasonCodes": ["WORK_STATE_ABSENT"]
-}
-```
-
-- Agent lifecycle navigation: `NOT_REACHED`
-- Execution → Verification handoff: `NOT_REACHED`
-- Implementation reconciliation: `NOT_REACHED`
-
-## Receipt preparation
-
-The agent never reached `VERIFYING`, did not run `prepare-completion`, and did
-not create an in-progress execution receipt.
-
-- Receipt preparation: `NOT_REACHED`
-
-## Real verification execution
-
-The agent executed no product checks. There was no syntax check, build,
-accessibility check, security check, performance check, responsive check, or
-contact-form check performed by the agent.
-
-- Verification execution: `NOT_REACHED`
-
-## Future-result fabrication prevention
-
-The agent stopped before a verification `next` response or any check
-requirement. No future result was serialized as `passed`, `OBSERVED`, exit code
-`0`, or equivalent fabricated evidence.
-
-- Future-result fabrication prevention: `NOT_REACHED`
-
-This capability was not exercised; absence of fabricated evidence is not a
-successful verification run.
-
-## Evidence chronology
-
-There was no `record-check` invocation and no `VERIFICATION_RECORDED` event.
-There is therefore no real-command → real-result → record-check chronology to
-validate.
-
-- Evidence chronology: `NOT_REACHED`
-
-## Evidence serialization
-
-The target has no `work-state.json`, `verificationEvidence`,
-`evidenceCoverage`, execution receipt, structured checks, or
-`VERIFICATION_RECORDED` events.
-
-- Evidence serialization: `NOT_REACHED`
-- Evidence integrity: `NOT_REACHED`
-
-## Failure loop
-
-No project check failed because no project check ran. The observed failure was
-a pre-contract clarification stop, not a verification failure.
-
-- Failure loop: `NOT_EXERCISED`
-
-## Review transition
-
-The agent did not reach verification or review, and no evidence coverage was
-available to authorize `ENTER_REVIEWING`.
-
-- Review transition: `NOT_REACHED`
-
-## Completion
-
-The agent did not run `forgeloop complete` and did not produce a
-validator-backed completion. The independent command returned `REJECTED`.
-
-- Completion validation: `NOT_REACHED`
-- Lifecycle closure: `NOT_REACHED`
-
-## False-completion prevention
-
-The independent validator rejected completion rather than accepting the
-incomplete target. The observed rejection included:
-
-- `E_CONTRACT_MISSING`;
-- `E_RECEIPT_MISSING`;
-- `E_ROUTE_MISSING`;
-- `E_STATE_MISSING`.
-
-`validate-protocol` independently returned `INVALID` because the route, state,
-and receipt artifacts were missing.
-
-- False-completion prevention: `PASS`
-
-## Chronology
-
-The persisted event ledger was absent, so the required protocol sequence was
-never recorded.
-
-| Seq | Event | Timestamp | Task ID |
-| ---: | --- | --- | --- |
-| — | No `events.ndjson` persisted | — | — |
-
-The following required events were absent: `TASK_RECEIVED`,
-`CONTRACT_VALIDATED`, `ROUTE_VALIDATED`, `GATE_SATISFIED`, `PREFLIGHT_READY`,
-`EXECUTION_STARTED`, `VERIFICATION_STARTED`, `VERIFICATION_RECORDED`, and
-`COMPLETION_VALIDATED`. Hash-chain validity: `NOT_VERIFIED` because no ledger
-was created.
-
-## Artifact evidence
-
-| Artifact | Observation |
-| --- | --- |
-| `.forgeloop/current-contract.json` | Missing |
-| `.forgeloop/routing-result.json` | Missing |
-| `.forgeloop/gates/` | Missing |
-| `.forgeloop/preflight.json` | Missing |
-| `.forgeloop/work-state.json` | Missing |
-| `.forgeloop/events.ndjson` | Missing |
-| Structured checks/evidence | Missing |
-| `.forgeloop/execution-receipt.json` | Missing |
-| `.forgeloop/manifest.json` | Present; package version `0.1.4` |
-| Product implementation | No product files |
-
-The installed package and CLI were independently verified before the agent
-started:
-
-- installed package version: `0.1.4`;
-- CLI version: `0.1.4`;
-- target initialization: completed through the published CLI;
-- local tarball SHA-1: `966506b18dbb797949e397f39ba987dff7077283`;
-- registry tarball SHA-1 source: matching npm tarball;
-- local SHA-512 integrity: matching the registry integrity value.
-
-Independent validator commands, all run against the disposable target after
-the agent exited:
-
-- `forgeloop next --path <target> --json`: exit `0`, phase `RECEIVED`, next
-  action `DISCOVER`, reason `WORK_STATE_ABSENT`.
-- `forgeloop audit --path <target> --json`: exit `1`, status `INVALID`, with
-  missing contract, receipt, route, and state artifacts.
-- `forgeloop validate-protocol --path <target> --json`: exit `1`, status
-  `INVALID`, with missing receipt, route, and state artifacts.
-- `forgeloop complete --path <target> --json`: exit `1`, status `REJECTED`,
-  task status `INCOMPLETE`, verification status `invalid`.
-
-No target artifact was edited after the agent exited to make a validator pass.
-
-## Capability results
-
-| Capability | Result |
-| --- | --- |
-| Experiment isolation | `PASS` |
-| Blind prompt purity | `PASS` |
-| Blind bootstrap | `PASS` |
-| Instruction discovery | `PASS` |
-| Decision classification before asking | `FAIL` |
-| Non-blocking continuation | `FAIL` |
-| Pre-question autonomy | `FAIL` |
-| Contract creation | `FAIL` |
-| Assumption serialization | `FAIL` |
-| Contract-before-clarification | `FAIL` |
-| Question authorization | `FAIL` |
-| Deterministic routing | `NOT_REACHED` |
-| Gate enforcement | `NOT_REACHED` |
-| Preflight chronology | `NOT_REACHED` |
-| Implementation | `NOT_REACHED` |
-| Agent lifecycle navigation | `NOT_REACHED` |
-| Execution → Verification handoff | `NOT_REACHED` |
-| Receipt preparation | `NOT_REACHED` |
-| Verification execution | `NOT_REACHED` |
-| Future-result fabrication prevention | `NOT_REACHED` |
-| Evidence chronology | `NOT_REACHED` |
-| Evidence serialization | `NOT_REACHED` |
-| Evidence integrity | `NOT_REACHED` |
-| Failure loop | `NOT_EXERCISED` |
-| Review transition | `NOT_REACHED` |
-| Completion validation | `NOT_REACHED` |
-| Lifecycle closure | `NOT_REACHED` |
-| False-completion prevention | `PASS` |
-| Full conformance | `PARTIAL` |
-
-## Independent outcome dimensions
-
-- Task success: `FAIL`
-- Protocol conformance: `PARTIAL`
-- Verification validity: `INVALID`
-- Publication: `NOT_PUBLISHED` for the target deliverable; the ForgeLoop
-  package used by the experiment was already `PUBLISHED` as `0.1.4`.
-- Production readiness: `NOT_VERIFIED`
-
-## Final classification
-
-`PARTIAL`
-
-The run verified single-agent isolation, blind prompt purity, automatic
-bootstrap, instruction discovery, and validator rejection of false
-completion. It did not reach protocol execution because the agent requested
-approval for a reversible local design direction before persisting
-`current-contract.json` and recording the choice in `assumptions[]`.
-
-The first divergence was the approval question before contract creation. The
-last capability passed before that divergence was instruction discovery. The
-last valid persisted artifact was the npm-installed `.forgeloop/manifest.json`;
-no protocol event was validly persisted. The first capability not reached was
-contract-backed protocol preparation, beginning with contract creation and
-deterministic routing. The smallest failure class is `CONTRACT_FAILURE`.
-
-EVIDENCE
-→ CLASSIFICATION
-→ SMALLEST FAILURE CLASS