Candidate focus cohort · maintained by Alejandro Sánchez
QZX Golden Core: a measured path from Alpha to Beta
Concentrate testing, contract review, real execution evidence, and compatibility work on a small set of high-frequency read-only commands before making stronger maturity promises.
Golden Core is a development focus cohort, not a separate edition, compatibility guarantee, certification, industry standard, or claim of external adoption. Every command keeps its independent lifecycle stage.
One cohort, two installation channels
Development stays measurable while the published Alpha remains immutable
The readiness board describes development checkout 0.2.2.0.7a5; the newest published pre-release is 0.2.2.0.7a5. The published package remains immutable while the next candidate can improve its evidence model. Pre-releases stay opt-in: a normal pip installation excludes them unless the operator passes --pre or selects the exact version.
Selection does not promote a command. Every selected capability remains independently assessed, and the current cohort is still entirely Alpha.
- Selected
- 15
- Beta-ready
- 0
- Dedicated tests
- 15
- Success captures
- 15
Eight independent dimensions
Progress that cannot hide its missing evidence
Tests, policy review, captured output, result contracts, platform evidence, release quality, and lifecycle promotion answer different questions. Passing one never substitutes for another.
Behavioral tests
15/15Maintained behavioral tests exercise the public command contract.
Policy review
15/15The safety and external-effect classification is reviewed against the current transitive implementation digest.
Successful execution
15/15A complete successful --json execution is captured and bound to the current implementation digest.
Failure or boundary evidence
15/15At least one representative failure or boundary result is captured when the command has a meaningful failure path.
Result contract review
15/15The implementation-backed result schema and documented domain fields are reviewed.
Relevant platform evidence
15/15Real execution evidence covers the operating systems and dependencies relevant to the command.
Release-quality review
15/15A machine-verifiable attestation binds an exact published release, verified artifacts, successful CI/platform evidence, zero known release blockers, and the current command implementation digest.
Lifecycle promotion review
0/15A machine-validated lifecycle review justifies any promotion beyond Alpha.
Current readiness status
Readiness follows the current implementation, not yesterday's score
All 15 selected commands now have a complete successful --json capture bound to the current implementation digest. This closes one evidence dimension; it does not replace platform outcomes, representative failures, release-quality review, or lifecycle promotion.
Failure or boundary evidence is resolved for 15 of 15 commands: 10 have a meaningful failed-result capture and 5 are explicitly marked not applicable instead of manufacturing an artificial failure. Current digest-bound platform evidence matches 15 of 15 commands across 10 CI environments and 150 command/environment executions. The exact-release quality attestation currently matches 15 of 15 current command implementations, while lifecycle promotion review covers 0 of 15. Any implementation or canonical-name change can reduce these counts until fresh evidence is earned; Beta-ready therefore remains derived from the current facts rather than preserved from an earlier release.
The selected command surface
Fifteen useful commands, each with visible blockers
Every card links to the complete command reference and derives its state from the current implementation digest, policy reviews, dedicated tests, lifecycle registry, controlled local captures, and any matching cross-platform CI evidence. No score is entered manually on this page.
system
version
7/8 resolved dimensions
Displays the installed QZX version and product identity
Lets an agent bind every later observation to the exact installed QZX version.
Failure/boundary: not applicable. The command has no caller-controlled domain input; forcing an artificial failure would not represent a useful public boundary.
Still required: Lifecycle promotion review.
system
listCommands
7/8 resolved dimensions
Lists all available commands organized by category
Makes the installed executable surface discoverable instead of relying on a prompt or remote documentation.
Failure/boundary: not applicable. An empty filter result is a valid discovery outcome, not a command failure.
Still required: Lifecycle promotion review.
system
help
7/8 resolved dimensions
Shows help for a command
Exposes parameters, examples, safety notes, and maturity before an operation is delegated.
Still required: Lifecycle promotion review.
system
getCurrentDateTime
7/8 resolved dimensions
Reports the current local date and time with timezone, calendar, ISO-week, and timestamp details
Provides timezone-aware date, calendar, and timestamp context without platform-specific shell syntax.
Still required: Lifecycle promotion review.
system
getCurrentDirectory
7/8 resolved dimensions
Shows the current working directory
Gives the current path and bounded directory context that agents frequently need before acting.
Failure/boundary: not applicable. The command observes the already-established process working directory; deterministic synthetic failure would test the harness more than the public domain contract.
Still required: Lifecycle promotion review.
system
getSystemInfo
7/8 resolved dimensions
Gets portable operating-system, Python, user, and environment information with optional RAM and storage details
Identifies the operating system, architecture, Python runtime, user context, and optional resource details.
Failure/boundary: not applicable. The default command has no required domain input; low-level platform API failure is environmental rather than a representative caller boundary.
Still required: Lifecycle promotion review.
system
getDiskSpace
7/8 resolved dimensions
Gets information about disk space usage
Reports raw and human-readable storage capacity before workflows create or transform data.
Still required: Lifecycle promotion review.
system
getRamInfo
7/8 resolved dimensions
Gets detailed information about system RAM usage
Reports current memory capacity and pressure for workload and troubleshooting decisions.
Failure/boundary: not applicable. The command has no caller-controlled domain input; a forced psutil or operating-system failure would be an infrastructure fault, not a useful contract example.
Still required: Lifecycle promotion review.
file
listFiles
7/8 resolved dimensions
Lists files in a directory with support for wildcards and recursive searching
Provides a familiar bounded file listing with wildcard and depth controls.
Still required: Lifecycle promotion review.
file
findFiles
7/8 resolved dimensions
Finds files by name, depth, size, and modification date with structured metadata
Finds files with explicit depth, size, date, exclusion, sorting, and truncation metadata.
Still required: Lifecycle promotion review.
file
findText
7/8 resolved dimensions
Searches for text patterns in files with advanced filtering options
Searches text with explicit matching, context, filtering, and result limits.
Still required: Lifecycle promotion review.
7/8 resolved dimensions
Calculates cryptographic hashes (MD5, SHA-1, SHA-256) of a file
Produces a reproducible cryptographic digest for identity and transfer verification.
Still required: Lifecycle promotion review.
development
getGitStatus
7/8 resolved dimensions
Provides a structured summary of the Git repository state (branch, remote, changes, recent commits)
Summarizes branch, remote, changes, and recent history without modifying the repository.
Still required: Lifecycle promotion review.
development
diagnoseProject
7/8 resolved dimensions
Inspects project technologies, dependencies, validation workflows, Git state, source quality, and large files without executing project scripts
Performs bounded static project inspection while keeping project-owned validation commands explicitly unexecuted.
Still required: Lifecycle promotion review.
network
checkUrlStatus
7/8 resolved dimensions
Requests an HTTP(S) URL and reports its status code, response time, and basic headers.
Adds one bounded network capability for HTTP status, latency, and basic response-header evidence.
Still required: Lifecycle promotion review.
Independent technical contribution
Provide a reproducible result, not a testimonial
Useful contributions include sanitized success and failure output, real platform runs, controlled native dependencies, counterexamples, security review, and a precise statement of what was not tested.
Bounded organizational pilot
Fund compatibility work without buying the conclusion
An organization can fund a defined platform matrix, a Result Contract interoperability pilot, or a release-quality review. Payment buys scoped work and evidence—not a favorable result, private control of the roadmap, or automatic Beta promotion.
Request a scoped assessmentA public engineering program associated with its creator
QZX Golden Core is maintained by Alejandro Sánchez. Its purpose is to make technical progress, uncertainty, and promotion criteria independently inspectable while QZX remains free and open source.