Developer Engagement

Conversations on Version 1 testing, technical assurance and operational readiness

FASO has reached an important transition point.

Its Version 1 technical foundation has been completed and subjected to extensive internal testing. The next stage is to test the system more broadly, challenge its assumptions, examine failure conditions and prepare carefully for an initial operational environment.

FASO is therefore beginning exploratory conversations with experienced developers and technical reviewers who may be interested in supporting this next phase.

This is not a call to invent FASO, redesign its governing method or develop speculative new features. The core Version 1 system already exists. The immediate need is for careful technical challenge, structured testing and implementation assurance.

Where FASO is now

Since April 2026, FASO has progressed from detailed architectural design into an implemented Version 1 system.

The system has been built to support governed, reproducible and verification-conscious observation of post-deployment AI change. Its internal architecture is designed to preserve clear distinctions between observation, validation, analysis, representation and evidential recording.

By the end of June 2026, the Version 1 implementation had completed extensive automated internal testing, with more than 24,000 tests passing and no recorded failures at the completion milestone.

This is an important engineering achievement, but it is not presented as independent validation. Internal testing can demonstrate consistency with the system’s own requirements; it cannot substitute for external technical challenge, independent review or operational experience.

FASO is now moving into a more demanding phase of end-to-end testing, assurance and controlled operational preparation.

The engagement we are seeking

FASO is interested in discussions with developers and technical specialists who understand that a successful build is only the beginning of assurance.

Areas of potential engagement include:

  • end-to-end and deterministic test design;

  • failure-mode and boundary-condition testing;

  • secure and controlled system architecture;

  • provenance, auditability and replay;

  • technical assurance and implementation review;

  • controlled data and evidence pipelines;

  • operational resilience;

  • reproducibility and test automation;

  • AI evaluation and post-deployment monitoring;

  • technical documentation and reviewability.

Engagement would be bounded and role-specific. It would not involve unrestricted access to the FASO system, protected methods or internal materials.

How engagement would begin

The first step would be an introductory conversation.

Its purpose would be to understand the developer’s experience, explain the current stage of FASO and identify whether there is a useful and appropriately bounded area for further discussion.

Where there is a clear fit, any subsequent engagement would be defined through a specific scope. That scope would identify the technical question being examined, the permitted access, the expected output and the relevant confidentiality, governance and publication boundaries.

No technical access would be assumed at the introductory stage.

Important boundaries

FASO’s technical and institutional safeguards must remain intact throughout any engagement.

Developer participation would therefore not create authority to:

  • alter FASO’s governing purpose or protected core principles;

  • redesign established evidential boundaries without proper authority;

  • gain unrestricted access to protected system components;

  • publish internal methods, thresholds or security-sensitive material;

  • represent participation as independent validation or endorsement;

  • deploy the system into live operation without governed approval.

FASO is not currently making a general employment, procurement or open-source invitation through this page. The purpose is to begin serious, exploratory conversations with people whose experience may be relevant to testing, assurance and operational readiness.

Why this matters

Post-deployment AI observability requires more than conceptual design. It requires systems that can be tested, replayed, challenged and shown to preserve their boundaries under difficult conditions.

FASO has built its first technical foundation. The next task is to determine how well that foundation holds when examined by experienced people who are prepared to test it carefully and constructively.

Developers or technical reviewers with relevant experience who would like to begin a conversation are invited to contact FASO through the website.