Publication disclosures

Record ID: LL-FDE-DISC-001
Version: 0.1.0
Status: public-draft disclosure record; incomplete fields remain publication blockers
Evidence cutoff: September 1, 2026

1. Publication identity

2. Funding and sponsor role

No finalized public funding statement or complete in-kind-support register is on record. Therefore this publication does not state that it received no funding, and it does not state that any outside sponsor funded, endorsed, reviewed, or influenced the work.

Before a citable release, the funding record must identify:

• direct organizational funding and staff time;
• grants, contracts, commissioned work, cloud or software credits, data access, and material in-kind support;
• funder or sponsor role in design, collection, analysis, interpretation, writing, publication, and access to data;
• restrictions, publication rights, and author independence;
• grant, contract, or internal project identifiers where applicable.

Current state: incomplete.

3. Competing interests

LockedIn Labs is the founder and current steward of the benchmark. It may also fund, train, employ, staff, recruit, evaluate, recommend, operate products for, or provide services to FDE practitioners and organizations. It may author benchmark methods, tasks, software, research, and public claims. Each role must be disclosed when it exists. These actual or potential combinations create financial, reputational, product, data-access, and decision conflicts that require disclosure, separation, recusal, and non-conflicted review.

Employment by LockedIn Labs, completion of LockedIn training, use of an affiliated or third-party platform, payment, sponsorship, friendship, employer prestige, or customer relationship cannot add benchmark credit.

No person-specific competing-interest statements or recusals are approved at this cutoff. See Authors, Contributors, and Publication Accountability, the Conflict of Interest Policy, and the Independence and Institutional Firewall.

4. Institutional independence

The project is at independence stage I0 — founding stewardship. No external-majority Commission, external chair, independent quorum, role-firewall assurance record, protected Commission budget, or independent appeal body is operational. No structural decision has been approved regarding a hosted autonomous program, separately governed affiliate, independent entity, or external certification body.

The current project therefore does not claim:

• independently governed or organizationally independent status;
• an official benchmark, official human result, official tier, or official credential;
• separation from LockedIn merely because policies or proposed outside roles exist;
• certification, accreditation, or conformance with ISO/IEC 17024, NCCA Standards, or another credentialing scheme.

The Independence and Institutional Firewall requires an external-majority FDE Benchmark Commission and operating role, data, funding, recusal, appeal, publication, and entity-decision controls before any official human output. Separate incorporation is treated as a structural option, not a universal scientific or legal requirement.

5. Human participants and ethics

No human-participant dataset is admitted to the benchmark repository. The registered commissioned-interview claim has zero records received and zero records eligible for public count at the cutoff.

No Institutional Review Board, research ethics committee, or equivalent approval, exemption, or non-applicability determination is claimed. No recruitment or real-data intake is authorized by this document.

Any future study must publish the responsible review authority, determination, consent or other lawful basis, withdrawal/correction path, privacy and security controls, and protocol version before intake.

6. Data and materials availability

Public specifications, ontology files, schemas, source documents, software, and conspicuously synthetic fixtures are available in the repository. No real candidate evidence, customer artifact, identity document, private repository, reference record, or production telemetry is admitted or released.

The synthetic reproducibility demonstration uses only the released synthetic scoring fixture and experimental scorer. It does not reproduce a human finding. See Synthetic Reproducibility Demonstration.

Operative code, content, and data licenses remain pending. Availability does not grant reuse rights beyond the terms actually present in the repository.

7. AI-assisted tools

OpenAI Codex has been used in the project workspace for repository inspection, source-assisted drafting, software implementation, and automated verification. AI-assisted systems have also been described in the project record at the category level.

The current disclosure boundary is:

Exact model identifiers, prompts, session logs, and complete AI-use provenance are not included in the current release package. A citable release must either provide the approved reproducibility-appropriate detail or explain what is withheld for security, privacy, or provider-policy reasons.

AI systems are not listed as authors or independent reviewers. The named human publication guarantor, once appointed, remains responsible for citations, confidentiality, code, calculations, and claims.

8. External and peer review

No external peer review, independent measurement review, independent validation, or independent reproduction is recorded.

Unfilled review roles include:

• independent occupational-measurement reviewer;
• senior FDE or enterprise deployment content reviewer;
• accessibility and accommodation reviewer;
• privacy/security reviewer;
• editorial and citation-integrity reviewer.

Future review records must disclose qualifications, scope, materials, method, funding, conflicts, disagreements, management response, date, and signed disposition. A review letter may support a bounded statement such as “externally reviewed for content completeness”; it does not by itself establish validation, independent governance, an external-majority Commission, or an official release.

9. Licenses, trademarks, and third-party rights

Operative public code/content licenses, contributor rights, trademark clearance, and third-party asset permissions are not complete. This blocks GL-2 citable archived draft status.

External standards and benchmark methods are cited as design inputs. No endorsement, partnership, copied protected taxonomy, or conformance is claimed.

10. Corrections, retractions, and reporting

The project defines correction, suspension, retraction, and retirement behavior in the Benchmark Publication Standard. A monitored public correction route, private security route, and private conduct route are not yet operational.

Current empirical publication count: zero. Current published empirical corrections or retractions: none, because no empirical finding has been published.

An absence of corrections is not evidence that the method is error-free.

11. Intended and prohibited use

The current draft supports public critique, construct and ontology research, synthetic implementation testing, and planning controlled studies.

It does not authorize official scoring, pass/fail, ranking, verified production records, capability profiles, tiers, credentials, certification, independent field validation, automated employment decisions, staffing recommendations, or intake of real evidence. The Benchmark Card, Independence and Institutional Firewall, and Live Versus Planned register control the exact current boundary.

12. Disclosure completion gate

Before GL-2 status, the release authority must approve:

• individual authors, CRediT contributions, guarantor, and corresponding contact;
• complete funding and in-kind-support statement;
• person-specific conflicts and recusals;
• release-specific AI-use statement and verification record;
• operative licenses and rights review;
• archive, DOI, canonical URL, citation metadata, and preservation owner;
• external review status stated with exact scope;
• independence stage, Commission status, role-firewall status, funding control, and structural-entity status;
• monitored correction, security, and conduct routes.

Current status: not complete; citable archived publication remains blocked.

Operational completion records, once real, must follow the Publication Integrity Workflow, Archive and DOI Deposition Packet, and Public Claim Receipt Operations. Their current presence is design evidence only, not a monitored route, deposit, DOI, review, or claim approval.