Plan your first bounded change.

Before you start

• Access to a repository you are allowed to change.
• Harness installed and configured for your environment, with its applicable guards active.
• A reviewer and a separate decision about what may be released.

These guides help you evaluate a configured environment. The website illustrations do not create accounts, connect repositories or ingest documents. Already invited? Find your workspace address. Need access? Ask about a configured setup.

Your first evaluation

1. Choose one small result

   Pick a change with an observable outcome: for example, correct an outdated setup instruction in one documentation file. Keep deployment, credentials and unrelated code outside this first task.

2. Write the boundaries

   Name the allowed files, the behavior to preserve and the actions that need a separate decision. Agree what should stop the task, including an unexpected need for wider access or scope.

3. Agree what will count as evidence

   Use the checks appropriate to that repository and change. Ask for the resulting diff, the checks actually run and their outcomes. A proposed command or a claim that a check passed is not the check result.

4. Review before moving forward

   Inspect the diff against the brief and examine failed or missing checks. Confirm the intended result yourself. Preparing a review packet does not authorize a merge or deployment.

A task brief to adapt

Objective: correct one outdated setup instruction.
Allowed change: the agreed documentation file only.
Preserve: application code, dependencies and configuration.
Evidence: the diff and the relevant documentation checks.
Success: a reviewer can follow the corrected instruction.
Stop if: the change needs secrets, wider scope or deployment.
Release: a separate decision by the authorized reviewer.

This is a plain-text planning aid. It is not executable work-order syntax, an installation command or permission to run anything.

What this establishes

You have a bounded task and a reviewable result. This first evaluation does not establish that every integration is sandboxed or that every command is covered by a guard.

Check execution and guard boundaries.