Focus Operating Framework v2026.09.05

Focus Operating Framework v2026.09.05

• Edition date: 2026-09-05 (UTC publication date)
• Predecessor: v1.1.0
• Scope: Documentation; substantive clarification and reduced recordkeeping

What changes for the individual

Recovery can begin without a cue or a workable time block. Missed routines do
not create catch-up debt. Rest, no new record and abandoning a private plan are
valid choices. Existing destination evidence can serve as an Action Receipt;
a second manual log is unnecessary when request, result and readback remain
inspectable. Releasing an intention does not cancel an external commitment or
authorize deleting someone else's records. Unknown outcomes remain unknown.

Compatibility and adoption

This edition relaxes duplicate recordkeeping and makes minimum practice explicit.
Readers or implementations requiring full cue templates, catch-up, uninterrupted
work or duplicate receipts should reconsider those requirements. The ten
commitments, six concerns, seven moves, individual authority, paper path,
selective admission, private Journal and optional derived Personal Mission
Control remain. AI is still optional, source-backed and unable to execute an
external mutation, including after confirmation.

Focus independently adopts Open Framework Commons v2026.09.05
at peeled commit 8868a248457dd7b663563beb243c5ebcbb8ac360, without deviations
from shared guidance or importing Commons tooling. No other product changes.

Calendar transition and release evidence

New editions use the actual UTC date, with .1, .2 for later editions on the
same date. Compare dates chronologically and suffixes numerically. The date does
not indicate compatibility or effectiveness. Historical v1.0.0 and v1.1.0 tags,
releases, citations, decisions, adoptions and reviews keep their exact identities.
No dated aliases are created. Product and Commons edition numbers are independent.

The release runbook separates these reader-facing notes from
assembly verification. The public release includes a separately delimited
attestation whose digest is carried in the annotated tag. The attestation covers
pre-publication assembly; publication is established by subsequent readback.

Evidence limits

The audit and scenario assessment tests textual
interpretation, scope and publication controls. Six review lenses are covered
by two independent reviewers; this is not six independent practitioner opinions.
The owner pilot remains NOT STARTED with zero counted episodes.
Practitioner evidence remains open.
No clinical, accessibility certification, universal performance or effectiveness
claim is supported. Historical v1.1.0 metadata used 2026-08-22 while actual public
publication occurred on 2026-08-23 UTC; those historical bytes are preserved.

Focus Operating Framework v2026.09.05 release-assembly attestation

• Role: Release assembly verifier
• Date: 2026-09-05
• Verdict: VERIFIED
• Reviewed content commit: c6bc52d3aeda0e8c08a98b6428a3b64cdd50c9c7
• Reviewed content tree: 45b9601192aa7190c1d3711a146e88e01ef06615
• Final candidate commit: 30bbbe25e2b6a4eca43dccc171e7293337152547
• Final candidate tree: 756d9816f1fa32229768d2416b75aa3574133946
• Commons tag: v2026.09.05
• Commons annotated object: 67914a6e305768206f1ead83dfcbc4325b951168
• Commons peeled commit: 8868a248457dd7b663563beb243c5ebcbb8ac360
• Commons tree: c139b847583e9550440ce6ac138b01cc8c710e89

Assembly boundary and approved bytes

Exact commits and trees were recomputed. The final candidate is clean. Its
complete difference from the reviewed candidate is exactly the seven additions
below, all predeclared in review governance and absent from the clean content
candidate. Each record is byte-identical to its approved external source. No
content, metadata, prompt, historical record or license changed after review.

Allowlisted record	SHA-256
project/reviews/v2026.09.05-accessibility-and-plain-language-review.md	3deb889a282d22ce1b0ea693576860a74edec35d2c295db212d5253611cbbdf4
project/reviews/v2026.09.05-adversarial-misuse-review.md	2299c0e3677d2185fb8ed2e05862177afdc8570be5e6fbaa0d84388be7c4721f
project/reviews/v2026.09.05-canonical-coherence-review.md	117b70ad4e4ed7adfa418d65362622b2aec85538c2cf6c5a9323a44147dc1740
project/reviews/v2026.09.05-practical-application-review.md	e0a335bd89ff6eb91f15531555741eeee2b23bd64c3cf2bf2b778e66802b6a58
project/reviews/v2026.09.05-public-hygiene-review.md	d790b5d0b80a76f65c58550fa195cdb4e66605af862458077d6e32995715af86
project/reviews/v2026.09.05-release-integrity-review.md	57e2eda21994810aa661a3586adfcf3b3dda486029a61210ba4d1b6fe65a0df6
project/reviews/v2026.09.05-review-disposition.md	32ae2b43a340b6239f2e359ddf3c7dd529e6fa2a47559fa1cf6be11f4090faa7

The six scoped reports all target the exact content candidate and return GO
with no findings. Two independent reviewers covered six lenses; these are not
six independent practitioner opinions. The disposition accounts for all findings,
limits, the rejected URL-count concern and open practitioner evidence. It
recommends GO to assembly, not a claim that publication already occurred.

Whole-tree checks

• PASS: 81 public files, 76 Markdown files, 189 parsed links and 811 headings;
  all local paths and heading targets resolve from the indexed public package.
• PASS: CFF 1.2 schema, quoted edition/date, canonical version/author/license,
  exact Commons pin, ten commitments, six concerns, seven moves and seven
  illustrative example structures.
• PASS: complete snapshot and Git-history redacted secret scans; publication
  hygiene inspection and report byte comparison. No secret or private
  attribution finding was identified.
• PASS: historical ADRs, specifications, reviews, pilot, release record, license
  and old changelog content preserved byte-for-byte. Both historical annotated
  objects, peeled commits, tagged assembly trees, seven review digests per
  release and original public-body attestation digests match readback.
• PASS: six review lenses, twenty adverse misuse cases and bounded minimum-use
  scenarios preserve human authority, uncertainty, rest and non-action choices.
• PASS: runbook shell and embedded publication/readback syntax. Existing main
  protections and signing policy remain unchanged; no executed failure was
  bypassed. No runtime, package, dependency, deployment or CI surface exists.

Limits and remaining publication gate

The owner pilot remains NOT STARTED; actual practitioner and specialist evidence
remains open in issue 10. These checks do not prove effectiveness, accessibility
certification, clinical value, live connector/provider behavior or absence of
all possible defects. Unchanged diagrams received no new rendered-layout claim.
Historical dates and candidate/public commit differences retain their stated
limits. Tag immutability is policy, not proof that an administrator cannot later
change remote state. No other repository or adoption changed.

VERIFIED for assembly of this exact final candidate. This attestation was
finalized outside the repository tree and has not verified the future merge,
Focus tag or public release. Publication requires the merged tree to equal this
final tree, an annotated tag carrying the detached digest, edition-facing notes
followed by these exact attestation bytes, and authenticated public readback.

Focus Operating Framework v1.1.0

Focus Operating Framework v1.1.0 release-assembly attestation

• Role: Release assembly verifier
• Verification date: 2026-08-22
• Verdict: VERIFIED

Exact identities

• Reviewed content-candidate commit: 98c37c29b105393daf547188020e41c26740c24a
• Reviewed content-candidate tree: 598bfb882b94a42a292acc1005264d262b6e3aa3
• Final-release-candidate commit: 3cbb2110419c031e7f7db78f4ecd251ced17d9fe
• Final-release-candidate tree: 227ff628ab5d2afec0c8a55f81177c19e100d2ea
• Adopted Commons release: v1.1.0
• Adopted Commons annotated tag object: 79e5f06dab46f262cad1d1daf7840e683ffc3880
• Adopted Commons peeled commit: f25a2b89b4aed95984fd235e2e229efe52c125d8
• Adopted Commons tree: 3216f7dc5dc0172df163bf50c13f57013a9125ff

Both candidate commits and trees were recomputed from the exact objects. Both
candidate worktrees were clean and contained no untracked material at the final
readback. The adopted Commons reference was confirmed as an annotated tag that
peels to the stated commit and tree. The Commons release precedes this Focus
release assembly. No tag or release was created or changed during verification.

Allowlist and complete candidate diff

The predeclared allowlist contains exactly these seven paths:

1. project/reviews/v1.1.0-practical-application-review.md
2. project/reviews/v1.1.0-adversarial-misuse-review.md
3. project/reviews/v1.1.0-canonical-coherence-review.md
4. project/reviews/v1.1.0-accessibility-and-plain-language-review.md
5. project/reviews/v1.1.0-public-hygiene-review.md
6. project/reviews/v1.1.0-release-integrity-review.md
7. project/reviews/v1.1.0-review-disposition.md

The complete tree comparison contains exactly seven additions and no other
change. The seven additions are exactly the seven allowlisted paths. None was
present in the reviewed content candidate. The candidate contained 61 tracked
files; the final assembly contains those exact 61 files plus the seven records,
for 68 tracked files total. No content file, prompt, README, policy, pilot
record, ADR, metadata file, or license changed after independent review. No
attestation, log, archive, temporary file, extra review record, symlink,
submodule, or executable entry appears in the final tree.

Review-record integrity

Each final record is byte-identical to its approved external source. The
SHA-256 values over the final and approved bytes are:

Record	SHA-256	Result
project/reviews/v1.1.0-practical-application-review.md	42d0262e796b698110c0c0ab8be46cce94ae10966f639006576e935414f72a07	Byte-identical
project/reviews/v1.1.0-adversarial-misuse-review.md	607606f388a7d3a6aab0d49c1eda06d56e2186eb1ce1771cd603d0912dee22ba	Byte-identical
project/reviews/v1.1.0-canonical-coherence-review.md	8e7f25626fea4e116af84c3260d91cc49183b6bedc9317cda200c440731a9fc2	Byte-identical
project/reviews/v1.1.0-accessibility-and-plain-language-review.md	d2d9c80fe44006f7dafd770c03ac4b92674d952e4ded9fd707342e5a2cbd4faa	Byte-identical
project/reviews/v1.1.0-public-hygiene-review.md	8ef129baac3bddebf31b07e058dabe85338e0a31e765ad3b2af784b4667f4675	Byte-identical
project/reviews/v1.1.0-release-integrity-review.md	b3e722bb87c9745cc4322e7ed47762fc893bf238e5a555e202fb826d8da8a837	Byte-identical
project/reviews/v1.1.0-review-disposition.md	91226d3887f5945710be22e6af1a2bbd444c5f32738318a9708154726d5ae7ce	Byte-identical

The six report digests match the digest table in the disposition. The complete
correction and rerun ledger digest is
f8402d9538335f31d3a28bb98aeaee4415ca01b86e100c06cfdf696961d9b71a,
matching the disposition.

All six independent reports identify the exact reviewed content-candidate
commit and tree, declare publication-safe reviewer roles, and return GO with
Blocker 0, Material 0, Minor 0, and Suggestion 0. Their source boundaries
exclude other current-release reports and dispositions, and the reviewed tree
contained none of those records, so no report reviewed itself or another
report. The disposition accounts for all six final reports, all prior graded
findings, the release-process standards conflict, every correction and rerun,
limitations, and material dissent. It returns GO and states that no unresolved
Blocker, Material, Minor, Suggestion, standards conflict, unsupported pilot
claim, target mismatch, unreviewed correction, or concealed material dissent
remains.

The seven records contain no private path, private provenance, assisting-system
identity, automated signature, generated-by attribution, credential, or
unapproved outside-source attribution.

Whole-tree verification results

• Required inventory: PASS. All 68 tracked files are readable, nonempty,
  regular files and match the required documentation release inventory.
• Markdown links and headings: PASS. All 63 Markdown files were checked:
  710 headings, 138 local links, and 43 heading targets produced no missing
  path, missing target, or duplicate generated heading identifier.
• Canonical framework: PASS. The name, definition, Mission, first job, ten
  commitments, six concerns, seven flexible moves, authority distinctions,
  individual scope, selective admission, paper path, optional AI boundary,
  optional Personal Mission Control, valid non-action outcomes, portable exit,
  and manual continuity remain consistent across canonical and release
  surfaces.
• Examples: PASS. All seven fictional, non-authoritative examples contain
  purpose and life scope, assumptions and limits, concerns and moves, provenance
  and authority, boundaries, an illustrative outcome, and subordinate lessons.
• Metadata and license: PASS. Focus Operating Framework, version 1.1.0,
  accepted status, founding steward and author, release date 2026-08-22, MIT
  license, citation metadata, changelog, version file, release specification,
  and release record agree. Citation metadata validates against CFF 1.2.
• Commons boundary: PASS. Current adoption surfaces consistently identify
  Commons v1.1.0 and peeled commit
  f25a2b89b4aed95984fd235e2e229efe52c125d8; the adoption decision and
  specification also preserve the exact annotated tag object and tree. Focus
  remains independently governed, and immutable earlier-release records retain
  their historical pin.
• Pilot status: PASS. The owner pilot remains Planned; no pilot results recorded, result NOT STARTED, with zero counted episodes, incomplete
  coverage, and no supported outcome claim. Pilot completion is not a
  prerequisite for this documentation release.
• Six reviews and disposition: PASS. All six verdicts and the disposition
  are GO, their target identities agree, and no unresolved finding or material
  dissent remains.
• Public hygiene: PASS. No private context, outside-source contamination,
  fabricated evidence, credential, or attribution leakage was found. External
  references are limited to the adopted Commons release and permitted
  first-party repository, proposal, prior-release, citation, and reporting
  destinations.
• Documentation-only boundary: PASS. The tree contains documentation and
  bounded repository templates only. It adds no application code, schema,
  provider-specific connector design, automation, CI, runtime behavior,
  technical conformance, certification, or outcome guarantee. Both tracked
  diagrams compiled, and the complete final snapshot produced no secret
  finding.
• Release plan consistency: PASS. Governance, specification, review
  workflow, disposition, assembly instructions, and post-merge instructions
  consistently require a merged tree identical to this verified final tree, an
  immutable annotated Focus tag carrying the detached attestation digest,
  release metadata containing these byte-identical attestation bytes, and
  authenticated public readback before publication is claimed.

Findings

No unresolved finding remains.

Limitations

This verification establishes exact assembly, documentation consistency, and
review-evidence integrity for the named objects. It does not establish real-use
effectiveness, safety, suitability, legal or clinical fitness, worldwide
textual originality, implementation behavior, connector behavior, rendered
accessibility in every environment, or a completed owner pilot.

The adopted Commons reference was verified at the stated object identities
during this pass. Later movement of an external reference would require fresh
readback and must not replace the exact adopted object identities recorded
here.

This attestation is stored outside the repository tree. It has not verified the
future merge, Focus tag, public release, release metadata publication, publisher
identity, or post-merge public readback. Those remain the required next gate.

Verdict

VERIFIED. The final-release-candidate contains the exact reviewed content
plus only the seven predeclared, approved, byte-identical review records and
disposition. All required assembly and whole-tree gates pass with no unresolved
release-blocking finding.

Focus Operating Framework v1.0.0

Focus v1.0.0 release-assembly attestation

• Role: Release assembly verifier
• Verification date: 2026-08-04
• Verdict: VERIFIED

Exact candidates

Candidate	Commit	Tree
Reviewed content candidate	66dd4570e9a36e9a7bb9edf7564808bdc75f66f1	d5186d21d58853d473e38ccfc331bce10db77671
Final release candidate	be2998afc08180353978a8fb71269196f89f3bdc	907ff4367d6b71ab0ee9f6a401247b02d08d2330

Both candidates resolved to the stated commits and trees. The reviewed content
candidate predates generated review-record placement. The final candidate was
inspected in a clean detached state with no changed, untracked, or ignored
material.

Adopted Commons release

• Release: Open Framework Commons v1.0.0
• Annotated tag object: d1303411ea67768ee2fee5dfb21e82c2e8599a3a
• Peeled commit: a0f0d384e9010a65d1a21a324b4c912433d5e031
• Tree: 965f839bfc545e183a0fdf04790baaaea8058626

The adopted tag is annotated and peels to the exact commit named throughout
the Focus candidate.

Candidate diff and allowlist

The complete diff from the reviewed content candidate to the final candidate
contains exactly these seven added paths:

1. project/reviews/v1.0.0-practical-application-review.md
2. project/reviews/v1.0.0-adversarial-misuse-review.md
3. project/reviews/v1.0.0-canonical-coherence-review.md
4. project/reviews/v1.0.0-accessibility-and-plain-language-review.md
5. project/reviews/v1.0.0-public-hygiene-review.md
6. project/reviews/v1.0.0-release-integrity-review.md
7. project/reviews/v1.0.0-review-disposition.md

These paths exactly match the predeclared generated-record allowlist. None
existed in the reviewed content candidate. No framework document, prompt,
policy, example, pilot record, ADR, metadata file, citation, or license changed
after independent review. No attestation, log, archive, temporary file, or
additional review record appears in the final tree.

Review-record byte identity

Every final-candidate record is byte-identical to its approved external source:

Record	SHA-256	Result
Practical application review	3181f099f4cb00d32c134f3be410f07ef90f6756d58737389e1dc9b23522f5c6	Identical
Adversarial misuse review	137db4d198d61cbc9176ebfc88abe6a0e6f07c1767bbe516ea2e583560abd60b	Identical
Canonical coherence review	bc5fb35d0fc5c88334658bfac0425bc4ab6c3ed4ed7fe21ed3a80823e59d203b	Identical
Accessibility and plain-language review	dbde4bd1f0ba636f08e206bf1eadfbf08aa547495b535aa20296249258156456	Identical
Public-hygiene review	b7d665d14ae537c8a9190e8b35ed1797e815789239173f3814d93e26a15195da	Identical
Release-integrity review	423658ab1fd0fd43282453078c0da38e81a5065814cb729c62a2c4496eca3c39	Identical
Review disposition	6fcc76e1441d751b8ca43864a313718fdca219c1343df1546dc2d26dfeb377e0	Identical

All six independent reports identify the exact reviewed content-candidate
commit and tree, provide accountable coverage and limitations, and return GO.
They do not review themselves or other reports. The disposition accounts for
the complete correction and rerun history, accepts the one current Minor
link-label limitation with rationale, and returns GO without concealing an
unresolved Blocker or Material finding.

Whole-tree checks

• The final tree contains 54 tracked files, including 52 Markdown files.
• Every local Markdown file link and heading target resolves.
• Heading structure, tables, fenced diagrams, and filename case pass.
• Both Mermaid diagrams render successfully and retain sufficient surrounding
  prose to communicate their meaning without the visual rendering.
• Framework name, version, author, charter status, changelog, citation, MIT
  license, governance, and publication boundary agree.
• Every Commons reference uses the exact adopted release and commit, preserves
  Focus independence, and makes no current ecosystem-membership claim.
• The owner-pilot protocol truthfully reports planned, not started, zero
  episodes, and no supported outcome claim.
• The framework remains documentation-only and contains no application code,
  schema, provider-specific connector design, automation, runtime, technical
  conformance, certification, or outcome guarantee.
• Public files contain no private context, private paths, credentials, outside
  source history, fabricated evidence, assisting-system attribution, or
  unsupported release claim.
• Secret, citation-structure, whitespace, and release-record hygiene checks
  pass.

Findings and limitations

No unresolved Blocker or Material finding remains. The accessibility review's
Minor link-label finding is explicitly accepted in the GO disposition because
the destinations remain identified, safe, and usable and exact identifiers
preserve adoption auditability.

This verification establishes only the assembly integrity of the exact final
candidate. It does not prove real-world effectiveness, implementation behavior,
security, privacy, accessibility certification, legal or clinical suitability,
pilot outcomes, public merge identity, tag creation, release publication,
authorship, or post-merge state.

The first public push may reproduce these verified trees in commits with
publication-safe authorship metadata. Those public commit identifiers may
differ from the pre-publication candidate identifiers above. The publication is
valid only when the public content tree and merged release tree remain exactly
d5186d21d58853d473e38ccfc331bce10db77671 and
907ff4367d6b71ab0ee9f6a401247b02d08d2330, respectively.

Verdict

VERIFIED. The final release candidate contains the exact reviewed content
plus only the seven predeclared, approved review records. Record bytes,
candidate identities, links, metadata, Commons adoption, pilot status,
documentation scope, visual rendering, hygiene, and release plan pass with no
unresolved release-blocking finding.

This attestation is outside the repository tree. It has not verified the future
merge, annotated tag, public release, or post-merge readback.