agentleFS
potentiavisionpotentiavision/partner-jarvis-starter/AGENTS.md

partner-jarvis-starter

AGENTS.md0 starsChanged 4 months agoMITView on GitHub

This repository belongs to the partner operating it. Never infer or import Joshua Garcia's identity, PotentiaVision client data, credentials, sessions, memory, or private system state. Before generation, building, designing, or external action: If required context is missing, stale, unreadable, or belongs to another project, stop and repair scope before durable work. Use: sense → decide → ask or act → verify → remember. Use Focusa project identity → Workpoint/trajectory orientation → execution → evidence capture → checkpoint. Operator steering overrides…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository6 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before generation, building, designing, or external action:

    line 9
  2. Distinctive:

    Verify the repository root.

    line 11
  3. Very specific:

    Read state/SESSION_STATE.md and the latest heartbeat report.

    line 17
  4. Distinctive:

    If required context is missing, stale, unreadable, or belongs to another project, stop and repair scope before durable work.

    line 20
  5. Distinctive:

    Use: sense → decide → ask or act → verify → remember.

    line 24
  6. Distinctive:

    Prefer the smallest reversible local change.

    line 27
  7. Distinctive:

    Verify outputs with tests or direct evidence before claiming completion.

    line 30
  8. Distinctive:

    Use Focusa project identity → Workpoint/trajectory orientation → execution → evidence capture → checkpoint.

    line 36

≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Partner Operator Agent Instructions

Identity boundary

This repository belongs to the partner operating it. Never infer or import Joshua Garcia's identity, PotentiaVision client data, credentials, sessions, memory, or private system state.

Mandatory startup hydration

Before generation, building, designing, or external action:

  1. Verify the repository root.
  2. Read config/operator_profile.json.
  3. Read state/ACTIVE_GOAL.json.
  4. Read state/SOURCE_OF_TRUTH_POLICY.json.
  5. Read state/SYSTEM_MAP.json.
  6. Read state/TOOL_CAPABILITY_MATRIX.json.
  7. Read state/SESSION_STATE.md and the latest heartbeat report.
  8. Resume the canonical Focusa Workpoint when available.

If required context is missing, stale, unreadable, or belongs to another project, stop and repair scope before durable work.

Operator loop

Use: sense → decide → ask or act → verify → remember.

  • Extend existing rails before creating new systems.
  • Prefer the smallest reversible local change.
  • External, credentialed, financial, destructive, installation, publishing, deployment, and production actions require exact operator approval.
  • A draft approval is not execution approval.
  • Verify outputs with tests or direct evidence before claiming completion.
  • Checkpoint Workpoints before risky work, project switches, compaction, or session end.
  • Store evidence handles and concise state, never secrets or raw private transcripts.

Focusa route

Use Focusa project identity → Workpoint/trajectory orientation → execution → evidence capture → checkpoint. Operator steering overrides advisory predictions and trajectories.

Completion reporting

Report files changed, checks run, actual results, remaining limitations, and one exact next action. Update local continuity and action logs after meaningful work.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.