lagune.charter

User Input

$ARGUMENTS

The User Input above decides how this command runs. Read it before proceeding.

Outline

You are creating or updating the project's security charter at .lagune/memory/charter.md: the set of safe-by-default principles that every later phase (detect, plan, harden, verify) must respect. This file is a TEMPLATE of placeholder tokens in square brackets (for example [PROJECT_NAME], [PRINCIPLE_1_NAME]). Fill it with concrete values and write it back.

This phase reads the project to decide which principles it needs, never to map what the code does with evidence. That mapping is the detect phase. The boundary is purpose, not depth: even when you read code here, you read it to derive a rule, not to record a finding.

Step 1: Load the charter and pick the mode

Load the charter at .lagune/memory/charter.md. If it does not exist, initialize it from template.md, next to this file, first, and identify every placeholder token of the form [ALL_CAPS_IDENTIFIER].

The User Input above selects one of two modes. The mode sets where the direction comes from, not how deep the reading goes (Step 2 governs that):