Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
236 changes: 236 additions & 0 deletions governance/OWNER_DECISION_20261025_RULES_LOOSENING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,236 @@
# OWNER DECISION — loosen process rules, keep the evidence and secret rails, 2026-10-25

Chief of Staff decision, 2026-10-25, about 11:37am CT. Dylan Roy approved this
package in chat with Grok Bot agent 15 on 2026-10-25 at about 12:32pm
America/Chicago. The APPROVED block in APPROVAL / EFFECTIVE GATE records that
approval. LOOSEN A–D and the supersession clauses are effective. KEEP remains
in force. Recorded by the Cursor cloud agent (Grok) on run
`bc-82abbe67-462d-5306-b58f-aa676cdd2496`, from that Chief of Staff decision
and from the source draft named below, with the approval block added on this
branch after the chat approval.

Scientific effect NONE. Credit 0. OBL OPEN. Not a result. Nothing here changes
a scientific status, flag, premise, prize or register.

This record is documentation only. It does not change GitHub settings, branch
protection, rulesets, or workflow YAML. The APPROVED block is recorded.
GitHub enforcement stays as it is until the owner edits rulesets and settings
himself. Agents do not make that settings edit, in this pull request or by a
bypass.

## APPROVAL / EFFECTIVE GATE

Dylan Roy approved this package in chat with Grok Bot agent 15 on 2026-10-25
at about 12:32pm America/Chicago. The message, as paraphrased for this record,
was "I approve" (typed "I alprove"). That chat is the basis of the block
below. The recorded approval is this APPROVED block.

APPROVED

- when: 2026-10-25 ~12:32pm CT (America/Chicago)
- who: Dylan Roy
- what: this package — KEEP and LOOSEN A–D as written in this file

The APPROVED block is present and complete. The gate is open. LOOSEN A–D have
operational effect. Supersession clauses bound to this block are effective.
KEEP remains in force.

The gate opens only by this block in this file, with all three fields. A
pull-request review, a package-approval widget, a green check, and a merge
commit do not replace it. The chat wording is the basis; this block is the
record that makes LOOSEN and the supersession clauses effective.

KEEP stays in force with the gate open. Truthful status labels stay in force:
unreviewed work is author-side or unreviewed, and is never labelled accepted.
Mathematics stays fail-closed: credit 0, OBL OPEN, and no PASS invented from
a hash. The owner's social security number stays withheld, and credentials
and tokens stay withheld. Agents still do not simulate another account's
approval or use a platform bypass they were not granted. Agents still do not
edit GitHub rulesets or repository settings.

With this APPROVED block recorded, LOOSEN A–D operate. Drive and Dropbox
identifiers, session identifiers, and file hashes may be public under A. The
owner may reduce required checks, review-thread resolution, and approval
counts on `main` by editing GitHub settings himself under B. Nonauthor review
is not a precondition for landing merges or docs under C. A lapsed claim
reopens after its stated lease under C. Workflow-file changes no longer wait
for owner approval via the Chief of Staff when a nonauthor review exists at
the exact head under C. Path-disjoint pull requests may merge in parallel
under D when the required checks are green and SHA guards are used. GitHub's
own enforcement stays as it is until the owner edits rulesets and settings.

Supersession of [OP-PRIVACY-20260927](OP-PRIVACY-20260927.md),
[OP-WORKFLOW-20260930](OP-WORKFLOW-20260930.md),
[OWNER_MANDATE_20261015](OWNER_MANDATE_20261015.md), the
[5 October Cursor decision](OWNER_DECISION_20261005_CURSOR.md), and the
[6 October surface decision](OWNER_DECISION_20261006_SURFACES.md) is effective
where those texts conflict with LOOSEN, because this APPROVED block is
recorded in this file. The historical texts stay on disk as evidence. Where
they conflict with LOOSEN, this package is the later reading. This file does
not change what GitHub enforces.

## Dylan's chat basis

The source draft records Dylan's chat instructions to session
`01B6fUVkWEba9KPrZjfHujFq` on 25 October 2026. Quoted from that draft:

> Private agent session info is not important and can be public for all I care. Privacy is not a concern at all unless it involves my social security number.

> rules should not stop scienctifc progress and if we find a rule is holding up changes it must be modified to allow to work to continue

> i want both lossened significantly

The third quotation is his answer when asked whether platform protections and
the scientific-status rule are covered. Spellings are his.

Package approval, later the same day: in chat with Grok Bot agent 15, at
about 12:32pm America/Chicago, Dylan Roy approved this package. The message,
as paraphrased for this record, was "I approve" (typed "I alprove"). The
APPROVED block above is the record of that approval.

## Source

`recovery/session_01B6fUVkWEba9KPrZjfHujFq/proposals_20261025/OWNER_RULES_LOOSENING_DRAFT.md`
at commit `05abf556819d3c8584ac2cd900707595e699cd4b`.

That path is on that commit. It is not on `main`, and this pull request does
not add the draft. The draft's own header calls it proposal text, not for
merge. This file is the decision record. It records the draft's items A–D as
the Chief of Staff package. The APPROVED block is in this file, so LOOSEN
A–D and the supersession clauses have operational effect. KEEP remains in
force.

The draft's lease bullet says "fixes #480". That parenthetical is not adopted
as a close. GitHub [#480](https://github.com/d6g8k5htny-coder/main/pull/480)
is the open zeta-fold documentation pull request about retained timing
streams. This decision does not close it.

## Policy

Loosen significantly, and keep the rails that protect evidence integrity and
secrets. Remove or rewrite process rules that stall scientific progress.

The KEEP and LOOSEN sections are the package Dylan approved, as named in the
APPROVED block.

The historical files stay on disk as evidence. This pull request does not
rewrite them. The mandate sentence on repository protections and independent
scientific acceptance requirements stays in
[the owner mandate](OWNER_MANDATE_20261015.md) (protection paragraph) as that
historical sentence. Supersession of that sentence,
[OP-PRIVACY-20260927](OP-PRIVACY-20260927.md), and
[OP-WORKFLOW-20260930](OP-WORKFLOW-20260930.md) is effective under the
APPROVED block in APPROVAL / EFFECTIVE GATE. Where those historical texts
conflict with LOOSEN, this package is the later reading. This file does not
change what GitHub enforces.

## KEEP

These rails stay in force.

1. **Status labels stay truthful.** Work that has not been reviewed is
labelled author-side or unreviewed. It is never labelled accepted.
2. **Mathematics stays fail-closed.** Credit stays 0. OBL stays OPEN. A
content hash, a green check, or a merge does not invent a PASS.
3. **Withhold the owner's social security number, and withhold credentials
and tokens.** Agents never simulate another account's approval. Agents
never use a platform bypass they were not granted.
4. **Agents do not edit GitHub rulesets or repository settings.** The
APPROVED block is recorded. The owner edits those settings himself.

## LOOSEN

Effective under the APPROVED block in APPROVAL / EFFECTIVE GATE. The
subsections below are the Chief of Staff's decision about what loosens and
what stays. They have operational effect. KEEP remains in force beside them.
GitHub's own enforcement stays as it is until the owner edits rulesets and
settings.

### A. Privacy

Effective under the APPROVED block in APPROVAL / EFFECTIVE GATE.

[OP-PRIVACY-20260927](OP-PRIVACY-20260927.md) withholds the owner's social
security number, and withholds credentials and tokens. Drive and Dropbox
identifiers, session identifiers, and file hashes may be public. When an
agent thinks some other item is private, the agent quotes it and asks the
owner to choose: (1) private, or (2) continue.

### B. Protections, workflow, and the owner mandate

Effective under the APPROVED block in APPROVAL / EFFECTIVE GATE.

Replace the ban on loosening repository protections and independent-acceptance
requirements with this owner authorization. The owner may reduce required
checks, review-thread resolution, and approval counts on `main`. He does that
in GitHub settings. The package approval is recorded. No agent holds that
access.

Platform restrictions and technical access denials still bind. An ungranted
bypass is still a denial. This file leaves every GitHub-enforced count as it
is. Required hosted checks remain required at the current tested commit until
the owner reduces them in those settings.

### C. Scientific status process

Effective under the APPROVED block in APPROVAL / EFFECTIVE GATE.

Nonauthor review is not a precondition for landing merges or docs. Nonauthor
review remains recommended. The source draft also treats a nonauthor review
as recommended, and not required, before a status label is updated. The label
still has to be true. Without a review, the label is author-side or
unreviewed.

An author replay is not a nonauthor review. When a review exists, the author
and the reviewer stay distinct people.

Same-provider review counts as a review. Record the provider.
Organizational-independence credit stays 0. That zero is a label. The review
still counts. Acceptance credit stays 0.

A lapsed claim reopens after its stated lease, without an explicit handoff.
A claim whose lease has not lapsed is unchanged by this sentence. This
sentence does not invent a release, and it does not close pull request #480.

Workflow-file changes no longer wait for owner approval via the Chief of
Staff. A nonauthor review at the exact head is enough. That sentence is
process text and is in effect. This pull request does not edit workflow YAML.
Until the owner edits GitHub settings, a workflow change still meets the
ruleset GitHub enforces today, still uses no ungranted bypass, and still has
that nonauthor review at the exact head.

### D. MAIN-LOCK

Effective under the APPROVED block in APPROVAL / EFFECTIVE GATE.

Allow parallel merges of path-disjoint pull requests when the required checks
are green and the merge uses SHA guards (`expected_head_sha` for the merge,
and a supported expected-old-ref guard for a branch update), instead of
taking one pull request at a time. This is process text and is in effect. It
does not install or remove a lock, and it does not change branch protection.
Path overlap, a failed check, or a SHA mismatch still stops the affected
merge. GitHub's current ruleset still binds until the owner edits it. The
APPROVED block is recorded, so that settings edit is his remaining step.

## What Dylan still does

The APPROVED block is recorded. LOOSEN has operational effect. KEEP remains
in force.

He edits GitHub rulesets and settings himself where he wants fewer required
checks, less review-thread resolution, or a lower approval count on `main`.
Until he makes those edits, GitHub enforcement is unchanged. Agents do not
make that settings edit.

## Unchanged

The historical files above, as evidence on disk. GitHub settings, branch
protection, rulesets, and workflow files, until the owner edits the settings
himself. Truthful status labels. Fail-closed mathematics, with credit 0 and
OBL OPEN. Withholding of the owner's social security number and of
credentials and tokens. The prohibition on simulating another account's
approval or using a bypass the platform has not granted. The
[5 October Cursor decision](OWNER_DECISION_20261005_CURSOR.md) and the
[6 October surface decision](OWNER_DECISION_20261006_SURFACES.md) yield on a
LOOSEN item because the APPROVED block in APPROVAL / EFFECTIVE GATE is
recorded in this file. Scientific effect of this file: NONE.