daniel/Artifex
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Artifex/docs/handoff_current_state_20260817.md
Daniel Maddern d61751a099 Add Guard model studio foundation
2026-08-17 01:04:02 +07:00

6.6 KiB
Raw Blame History

Artifex Handoff - Current State - 2026-08-17

Current Objective

We have been repairing and dogfooding the CRYPTO / PROTOCOL VENTURE COHORT pipeline, specifically the V0.3.1 cohort and the V0.3.2B token-judge evidence repair.

Hard constraint: NO NEW IDEAS for the repair work. Only reprocess the existing six former V0.3.1 survivors.

Safety constraints remain active:

  • Do not issue or sell native tokens.
  • Do not sell NFTs or memberships.
  • Do not launch mainnet.
  • Do not create liquidity or market make.
  • Do not contact investors, users, or customers.
  • Do not fundraise.
  • Do not spend real money.

Environment

  • Workspace: S:\PycharmProjects\Artifex
  • Repo remote: http://192.168.1.162:3000/daniel/Artifex.git
  • Database: sqlite:///db.sqlite3
  • SearXNG: http://192.168.1.162:8080
  • Qwen: http://192.168.1.162:8002
  • Current date in environment: 2026-08-17
  • Known harmless push warning: git: 'credential-manager-core' is not a git command. See 'git --help'.

Spark remote validation was previously blocked by SSH auth:

  • daniel@192.168.1.162: Permission denied (publickey,password).

Current Cohort

  • Cohort ID: CPV031-20260816215626-66d636b2
  • GraphRun: 10
  • Existing six former V0.3.1 survivors only:
    • Agent Passport Clearinghouse
    • PatchBond Network
    • ProofGrid Compute Attestation Network
    • ProofBond
    • Compute Clearance Network
    • ProofGrid Compute Escrow

Latest Implemented Work

V0.3.2B Token Judge Evidence Repair

Implemented strict Sol Token Utility Judge evidence validation.

Required non-empty fields now enforced:

  • argument_for_native_token
  • argument_against_native_token
  • external_collateral_counterfactual
  • native_token_removed_breaks
  • native_token_removed_explanation
  • material_improvements_over_USDC_ETH
  • native_asset_costs_and_risks
  • final_rationale

Behavior now:

  • Rejects incomplete Sol judge response.
  • Retries incomplete judge response up to 3 attempts.
  • Raises ValueError after exhausted retries.
  • Does not fall back to deterministic/heuristic classification when Sol produced an incomplete response.
  • Normalizes Sol response when external_collateral_counterfactual appears nested under counterfactual_analysis.
  • Uppercases utility_scores keys during normalization.
  • Persists final_rationale in token metadata as well as TokenUtilityAssessment.rationale.
  • crypto_score_row() now reuses persisted token_utility_assessment instead of calling the token judge again.
  • Final Sol IC prompt was compacted so it returns usable JSON.

Rationale invariants now checked:

  • Every TOKEN_OPTIONAL rationale must explain why ETH/USDC/external collateral is preferable despite claimed degradation.
  • Every TOKEN_ESSENTIAL / TOKEN_STRONGLY_JUSTIFIED rationale must explain what protocol-specific property cannot be reproduced economically enough with ETH/USDC/external collateral.
  • The code does not automatically promote due to material degradation.

Latest Six-Proposal Results

Before/after classifications from V0.3.2B:

Company Before After Score Final IC Decision Final IC Score Required Field Gaps
Agent Passport Clearinghouse TOKEN_OPTIONAL TOKEN_UNNECESSARY 18.0 REJECT_TOKEN_NOT_NEEDED 62.3 []
PatchBond Network TOKEN_OPTIONAL TOKEN_OPTIONAL 48.0 REJECT_TOKEN_NOT_NEEDED 66.4 []
ProofGrid Compute Attestation Network TOKEN_OPTIONAL TOKEN_OPTIONAL 42.0 REJECT_TOKEN_UTILITY_WEAK 63.6 []
ProofBond TOKEN_OPTIONAL TOKEN_OPTIONAL 54.0 REJECT_TOKEN_UTILITY_WEAK 64.3 []
Compute Clearance Network TOKEN_OPTIONAL TOKEN_STRONGLY_JUSTIFIED 78.0 PROTOCOL_VALIDATE 79.7 []
ProofGrid Compute Escrow TOKEN_OPTIONAL TOKEN_OPTIONAL 58.0 REVISE_TOKEN_MODEL 67.9 []

Current corrected cohort state:

  • Token unnecessary: 1
  • Token optional/routed SaaS: 4
  • Token strongly justified: 1
  • Token essential: 0
  • Serious crypto survivors: 0
  • Crypto survivors: 0
  • Autonomous crypto survivors: 0
  • Assisted high-potential: 0
  • Finalists: 0
  • V0.3.2B required field gaps: 0
  • Token red-team failures:
    • TOKEN_NOT_REQUIRED: 5
    • YIELD_DEPENDENCY: 1
    • SLASHING_DEPENDS_ON_HUMAN_JUDGMENT: 1

Important nuance: Compute Clearance Network became TOKEN_STRONGLY_JUSTIFIED, but final cohort finalists remain 0. It is not automatically promoted to finalist.

Latest Files Changed

  • agents/crypto_venture.py
    • Strict token judge evidence validation/retry/fail-closed behavior.
    • Token judge response normalization.
    • Persisted required fields.
    • Reused persisted token assessment in crypto_score_row().
    • Compact final Sol IC prompt.
  • tests/test_crypto_venture_cohort.py
    • Added coverage for complete required judge fields.
    • Added retry-success and retry-exhaustion/fail-closed tests.
  • control_plane/ventures/management/commands/export_crypto_venture_cohort.py
    • Added V0.3.2B Before/After markdown section.
  • docs/crypto_venture_cohort_v031_20260816.md
    • Updated exported V0.3.2B report.
  • docs/crypto_venture_cohort_v031_20260816.json
    • Updated exported V0.3.2B report data.

Latest Commits Pushed

Recent relevant commits:

  • 35d3346 Repair crypto token judge evidence export
  • 6e89ea8 Require complete crypto token judge evidence
  • 052d1fc Add corrected crypto cohort V0.3.1 export
  • 94b9ab6 Repair crypto token utility scoring
  • 54ffe92 Add crypto protocol cohort V0.3.1 export

The most recent push succeeded to main with the known harmless credential-manager warning.

Verification

Latest verification passed:

  • python manage.py check: passed
  • python -m pytest -p no:django -q tests/test_crypto_venture_cohort.py: 14 passed
  • Full suite: 157 passed, 1 skipped

Warnings are existing Python/Django/LangGraph deprecation warnings and pytest collection warnings for TestRun; no failing tests.

Current Git State At Time Of Handoff

After the latest commit/push, git status --short was clean.

This handoff file itself is newly added after that push and should be committed/pushed if the user wants the note persisted remotely.

If Continuing

Recommended next steps only if the user asks to continue:

  1. Commit and push this handoff note if desired.
  2. If further V0.3.2B analysis is requested, inspect docs/crypto_venture_cohort_v031_20260816.md first.
  3. Do not regenerate ideas unless explicitly instructed.
  4. Do not rerun broad research unless explicitly requested or needed for a new judge repair.
  5. Keep all token/mainnet/fundraising/user-contact/no-spend stop conditions active.