Skip to content

Unattended runs: explicit path through the §0 style gate (policy proposal) #262

Description

@YahyaZekry

Problem

§0 of the skill says: "Don't silently ship default-skinned diagrams into a branded project" — and the first-run style gate enforces this by pausing and asking the user.

In an unattended run (autonomous session, batch pipeline, scheduled agent), there is no user to ask. Today the run has only two options: stall forever on the gate, or proceed silently — which is exactly what §0 forbids. From a real production run: a multi-diagram dossier hit the gate mid-run with nobody reachable, and the only path forward was improvising around the skill text.

Proposal

Add an explicit unattended branch to the §0 gate:

If no user is reachable, take the explicit-default path (e) and state beside the deliverable that the default skin was used and can be restyled on request — never silent.

The choice is recorded and surfaced, so the branding guarantee is preserved in spirit: the default is never passed off as a deliberate skin. Interactive behavior is unchanged — when a user is reachable, the gate asks exactly as before.

Why an issue

Flagged by the maintainer in #240: this is a policy change to §0, and CONTRIBUTING asks for an issue first. The PR that surfaced it (#240) has been reduced to its uncontroversial half (font-substitution guidance in primitives-core.md).

Happy to turn this into a PR once there's a direction call from the maintainer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions