Enter the FieldParallax World Portal
Projects/QForge

Project Genome · QF-001

QForge

A quantum-workstation architecture that distinguishes virtual and physical QPU states and refuses to launder simulation into hardware claims.

draftCore canonTier 1
QForge project field card
Registry-bound visual · B4
RegionPhi369 Labs
Status Exploring
MaturitySprout
EvidenceResearch-grounded
Visibilitypublic candidate
RecordUpdated 2026-07-25
Guided appearances
Understand

01

Origin condition

Why it exists

Quantum software often blurs simulation, emulation, cloud access, and physical execution. QForge exists to make execution class and evidence impossible to hide, so a useful workstation can explore quantum workflows without laundering virtual results into hardware claims.

Can one workbench support learning and experimentation while preserving the difference between simulated and physical quantum execution?

02

Working system

What it does

  • Q
    Runs classified workloads

    Labels execution from E0 conceptual work through E5 verified physical execution.

  • MIU
    Checks model integrity

    The Model Integrity Unit records backend identity, assumptions, noise, compilation, and evidence.

  • ⌁
    Preserves run receipts

    Every circuit, backend choice, transformation, result, and interpretation can be retained as a lineage record.

03

System anatomy

Architecture

QForge combines a circuit workspace, execution-class governor, virtual and physical backend adapters, Model Integrity Unit, and result ledger.

01designed

Workbench

Circuit, algorithm, dataset, and notebook authoring.

02designed

Execution governor

E0–E5 classification and backend eligibility rules.

03planned

Backend adapters

Transparent simulator first; physical providers only through verified connectors.

04designed

Model Integrity Unit

Receipts for transpilation, noise model, backend, measurement, and interpretation.

04

Present tense

Current state

QForge is recorded as Exploring at the Sprout stage. The inventory currently marks 4 artifact lanes Ready, 2 Partial, and 2 Missing.

SeedSproutGrowingCanopyStewarded

B3 Tier 1 room draft · Core canon · Research-grounded evidence · public candidate

05

Honest edges

Known limitations

  • No physical QPU integration or verified E5 run is represented in the current portal record.
  • Simulation fidelity depends on the stated model and cannot reproduce every hardware effect.
  • Quantum advantage is workload-specific and is not assumed.
  • Provider terms, cost, queueing, privacy, and export controls would require separate review.

06

Claim boundary · v1.1.0

What we are—and are not—saying

Supported

A master architecture, execution classes E0–E5, virtual/physical state distinction, Model Integrity Unit, and no-trust-laundering rule have been specified.

Not claimed

QForge is not represented as a physical quantum computer, proof of quantum advantage, certified benchmark platform, or substitute for provider verification.

07

Development memory

Ledger

B3-QF-001-01
Architecture

Virtual and physical QPU states separated in the QForge design.

✓ Documented
B3-QF-001-02
Governance

Execution Classes E0–E5 and Model Integrity Unit defined.

✓ Documented
B3-QF-001-03
Portal

Tier 1 workbench room drafted with transparent simulator-first boundary.

✓ Draft

Curated project receipts · source-file binding and human review remain pending

08

Directional, revisable

Roadmap

01
Now

Freeze the execution receipt

Define the minimum metadata required for every E0–E5 result.

02
Next

Build the transparent simulator

Create a local demonstration that never labels simulation as hardware execution.

03
Later

Add verified provider adapters

Integrate physical backends only when identity, custody, cost, and evidence can be recorded.

10

B10 evidence trail

Featured evidence

registry bound

Registry-grounded trail

No primary source package is bound yet. The public trail is limited to the verified field card and public Genome snapshot.

QForge evidence board
visual · project-card

QForge — Project Field Card

B4-generated visual identity card built directly from the reviewed constellation registry.

Open bound artifact
data · genome-snapshot

QForge — Public Genome Snapshot

Public-safe JSON snapshot of the current project registry or expanded Project Genome.

Open bound artifact
Open the full evidence board

11

Publication intake

Artifacts & sources

Detail roomPartial
SummaryReady
Hero / posterPartial
SpecificationsReady
Demo / repositoryMissing
Public linkMissing
Claim boundaryReady
RelationshipsReady
design-specindexed

QForge Master Architecture

Execution classes, MIU, and backend boundaries.

View archive recordarchive:intake/qforge-master-architecture
demomissing

Transparent local simulator

Planned first executable demonstration.

View archive recordarchive:intake/qforge-simulator
schemaindexed

Execution receipt schema

Core fields are designed; canonical machine-readable form remains to be frozen.

View archive recordarchive:intake/qforge-execution-receipt

Source basis

QForge master architecturearchive:intake/qforge/source-basisarchive-canon
Enter the Field B3 Tier 1 room draftportal:project/qforge@v0.4-b3planning-inventory

Review: Canon, claims, privacy, accessibility, and publication review · pending

12

Move with evidence

Next actions

primaryInspect the execution boundary

Every result should tell you what actually executed, where, and under which assumptions.

reviewReview the artifact register

See which source packages, visuals, demonstrations, and public links are actually ready.

secondaryTrace related projects

Follow documented dependencies and neighboring systems without inventing connections.