red-methodology 0.1.0__tar.gz

red_methodology-0.1.0/.gitignore

@@ -0,0 +1,21 @@
+node_modules/
+dist/
+build/
+*.egg-info/
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.coverage
+.venv/
+cli/node/bundled/
+cli/python/src/red_cli/bundled/
+cli/node/LICENSE
+cli/node/NOTICE
+cli/python/LICENSE
+cli/python/NOTICE
+.tmp/
+/.agents/
+
+# This repository keeps its RED working state local.
+/research/
+/evolve/

red_methodology-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 exoticknight
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

red_methodology-0.1.0/NOTICE

@@ -0,0 +1,2 @@
+RED
+Copyright 2026 exoticknight

red_methodology-0.1.0/PKG-INFO

@@ -0,0 +1,36 @@
+Metadata-Version: 2.5
+Name: red-methodology
+Version: 0.1.0
+Summary: Deterministic project operations for the RED methodology
+Project-URL: Homepage, https://github.com/exoticknight/red
+Project-URL: Repository, https://github.com/exoticknight/red
+Project-URL: Issues, https://github.com/exoticknight/red/issues
+Author: exoticknight
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Keywords: agent,ai,documentation,methodology,red
+Classifier: Development Status :: 3 - Alpha
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.11
+Requires-Dist: jsonschema<5,>=4.25
+Description-Content-Type: text/markdown
+
+# RED CLI for Python
+
+This package is the Python distribution of the RED methodology CLI. It provides deterministic project initialization, artifact creation and promotion, structural validation, Skill lifecycle management, and lightweight instruction export.
+
+```sh
+pipx run --spec red-methodology red version
+pipx run --spec red-methodology red skill install --scope repo
+pipx run --spec red-methodology red init
+pipx run --spec red-methodology red check --json
+```
+
+The CLI handles deterministic project files and validation. A human or project-authorized process decides when Research enters Evolve and when Evolve enters Document; promotion flags record that decision.
+
+The Node distribution exposes the same command contract. See the [CLI specification](https://github.com/exoticknight/red/blob/main/spec/cli-interface.md).

red_methodology-0.1.0/README.md

@@ -0,0 +1,14 @@
+# RED CLI for Python
+
+This package is the Python distribution of the RED methodology CLI. It provides deterministic project initialization, artifact creation and promotion, structural validation, Skill lifecycle management, and lightweight instruction export.
+
+```sh
+pipx run --spec red-methodology red version
+pipx run --spec red-methodology red skill install --scope repo
+pipx run --spec red-methodology red init
+pipx run --spec red-methodology red check --json
+```
+
+The CLI handles deterministic project files and validation. A human or project-authorized process decides when Research enters Evolve and when Evolve enters Document; promotion flags record that decision.
+
+The Node distribution exposes the same command contract. See the [CLI specification](https://github.com/exoticknight/red/blob/main/spec/cli-interface.md).

red_methodology-0.1.0/pyproject.toml

@@ -0,0 +1,36 @@
+[build-system]
+requires = ["hatchling>=1.27,<2"]
+build-backend = "hatchling.build"
+
+[project]
+name = "red-methodology"
+version = "0.1.0"
+description = "Deterministic project operations for the RED methodology"
+readme = "README.md"
+requires-python = ">=3.11"
+license = "Apache-2.0"
+authors = [{ name = "exoticknight" }]
+dependencies = ["jsonschema>=4.25,<5"]
+keywords = ["ai", "agent", "documentation", "methodology", "red"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "License :: OSI Approved :: Apache Software License",
+  "Programming Language :: Python :: 3 :: Only",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+]
+
+[project.urls]
+Homepage = "https://github.com/exoticknight/red"
+Repository = "https://github.com/exoticknight/red"
+Issues = "https://github.com/exoticknight/red/issues"
+
+[project.scripts]
+red = "red_cli.cli:main"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/red_cli"]
+
+[tool.hatch.build.targets.sdist]
+include = ["src/red_cli", "README.md", "LICENSE", "NOTICE"]

red_methodology-0.1.0/src/red_cli/__init__.py

@@ -0,0 +1,4 @@
+"""RED methodology command-line interface."""
+
+__version__ = "0.1.0"
+PROTOCOL_VERSION = 1

red_methodology-0.1.0/src/red_cli/bundled/protocol/artifact-schema.json

@@ -0,0 +1,60 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://github.com/exoticknight/red/blob/main/spec/artifact-schema.json",
+  "title": "RED Protocol 1 artifact metadata",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["id", "state", "status", "title", "created"],
+  "properties": {
+    "id": { "type": "string" },
+    "state": { "enum": ["research", "evolve"] },
+    "status": { "enum": ["open", "closed", "accepted", "rejected"] },
+    "title": { "type": "string", "minLength": 1 },
+    "created": {
+      "type": "string",
+      "format": "date",
+      "pattern": "^[0-9]{4}-(0[1-9]|1[0-2])-([0-2][0-9]|3[01])$"
+    },
+    "based_on": {
+      "type": "array",
+      "uniqueItems": true,
+      "items": { "type": "string", "pattern": "^[RE]-(?:[1-9][0-9]*|0[0-9]{3})$" }
+    },
+    "document_paths": {
+      "type": "array",
+      "minItems": 1,
+      "uniqueItems": true,
+      "items": {
+        "type": "string",
+        "minLength": 1,
+        "allOf": [
+          { "not": { "pattern": "^(?:[A-Za-z]:|/|\\\\)" } },
+          { "not": { "pattern": "(^|[\\\\/])\\.\\.([\\\\/]|$)" } }
+        ]
+      }
+    },
+    "verified": { "type": "boolean" }
+  },
+  "allOf": [
+    {
+      "if": { "properties": { "state": { "const": "research" } }, "required": ["state"] },
+      "then": {
+        "properties": {
+          "id": { "type": "string", "pattern": "^R-(?:[1-9][0-9]*|0[0-9]{3})$" },
+          "status": { "enum": ["open", "closed"] }
+        }
+      }
+    },
+    {
+      "if": { "properties": { "state": { "const": "evolve" } }, "required": ["state"] },
+      "then": { "properties": { "id": { "type": "string", "pattern": "^E-(?:[1-9][0-9]*|0[0-9]{3})$" } } }
+    },
+    {
+      "if": { "properties": { "status": { "const": "accepted" } }, "required": ["status"] },
+      "then": {
+        "required": ["document_paths", "verified"],
+        "properties": { "verified": { "const": true } }
+      }
+    }
+  ]
+}

red_methodology-0.1.0/src/red_cli/bundled/protocol/config-schema.json

@@ -0,0 +1,57 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "https://github.com/exoticknight/red/blob/main/spec/config-schema.json",
+  "title": "RED Protocol 1 configuration",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["version", "document", "research", "evolve", "policy"],
+  "properties": {
+    "version": {
+      "type": "integer",
+      "minimum": 1,
+      "maximum": 9007199254740991
+    },
+    "document": { "$ref": "#/$defs/document" },
+    "research": { "$ref": "#/$defs/artifactDirectory" },
+    "evolve": { "$ref": "#/$defs/artifactDirectory" },
+    "policy": { "$ref": "#/$defs/policy" }
+  },
+  "$defs": {
+    "relativePath": {
+      "type": "string",
+      "minLength": 1,
+      "allOf": [
+        { "not": { "pattern": "^(?:[A-Za-z]:|/|\\\\)" } },
+        { "not": { "pattern": "(^|[\\\\/])\\.\\.([\\\\/]|$)" } }
+      ]
+    },
+    "document": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["paths"],
+      "properties": {
+        "paths": {
+          "type": "array",
+          "minItems": 1,
+          "uniqueItems": true,
+          "items": { "$ref": "#/$defs/relativePath" }
+        }
+      }
+    },
+    "artifactDirectory": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["path"],
+      "properties": { "path": { "$ref": "#/$defs/relativePath" } }
+    },
+    "policy": {
+      "type": "object",
+      "additionalProperties": false,
+      "required": ["document_requires_approval", "report_document_implementation_conflicts"],
+      "properties": {
+        "document_requires_approval": { "type": "boolean" },
+        "report_document_implementation_conflicts": { "type": "boolean" }
+      }
+    }
+  }
+}

red_methodology-0.1.0/src/red_cli/bundled/skill/red/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: red
+description: Manage project knowledge and engineering changes with Research, Evolve, and Document. Use when the user requests RED, or when a repository declares RED through red.toml, RED.md, or AGENTS.md. Do not impose RED on undeclared projects.
+metadata:
+  red-protocol: "1"
+---
+
+# RED
+
+Keep accepted knowledge, unresolved research, and ongoing change distinct.
+
+## Knowledge and authority
+
+- Document is the normative baseline for people and agents using, maintaining, or changing the project. Organize accepted knowledge and necessary rationale around their tasks; keep R/E record references, provenance, and work history on the R/E side. Use the Document writing guidance in `references/artifacts.md` when drafting or updating it.
+- Research holds unverified evidence, claims, and questions. Evolve holds proposed or ongoing change and unresolved alternatives.
+- Code, tests, configuration, and runtime output are implementation evidence. Investigate and report conflicts with Document before choosing a side.
+- At an R/E boundary, present the reviewable result and wait for a separately authorized transition. A broad earlier request does not supply that decision. Update Document only after acceptance.
+- Preserve existing documentation structure and project storage/version-control policy. Keep small, resolved work in the task; persist consequential or shared work using the criteria in `references/work.md`.
+
+## Load context on demand
+
+1. Follow applicable repository instructions. Read `red.toml` when present; otherwise locate likely Document sources. Create configuration only for requested adoption or deterministic operations needing a mapping.
+2. Read the reference for the current route below. Load additional references only when their operation becomes necessary; links are lookup targets, not a recursive reading list.
+3. Find relevant Document sections, active E items, R evidence, and implementation with filenames, headings, or scoped search before reading bodies. Widen the search when dependencies or conflicts require it.
+4. Reuse instructions and evidence already available in context. Re-read changed sections, or missing material after compaction, rather than restarting discovery each turn. Keep tool output focused on relevant excerpts and results.
+
+## Routes
+
+- Engineering work and E maintenance: [work.md](references/work.md).
+- First-time or brownfield adoption: [adopt.md](references/adopt.md).
+- Project health checks: [inspect.md](references/inspect.md).
+- Creating/promoting artifacts or drafting/updating Document: [artifacts.md](references/artifacts.md).
+- Using, enabling, or falling back from the CLI: [cli.md](references/cli.md).
+- Unclear state semantics: [protocol.md](references/protocol.md); unfamiliar routing cases: [scenarios.md](references/scenarios.md).
+
+## Finish
+
+Reconcile active E with current decisions, evidence, remaining work, and open alternatives. Report verification, conflicts, and unknowns; apply the transition boundary above. Run `red check --json` when the CLI is available, and state when it could not run.

red_methodology-0.1.0/src/red_cli/bundled/skill/red/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "RED"
+  short_description: "Manage project knowledge through RED states"
+  default_prompt: "Use $red to handle this project task with the RED methodology."
+
+policy:
+  allow_implicit_invocation: true

red_methodology-0.1.0/src/red_cli/bundled/skill/red/assets/AGENTS.fragment.md

@@ -0,0 +1,5 @@
+<!-- red:start protocol=1 -->
+## RED workflow
+
+Use Research for unresolved evidence and questions, Evolve for proposed or ongoing changes, and Document for accepted project knowledge. A clear change may enter Evolve directly. After Research, report findings and wait for explicit authority before Evolve. After Evolve passes verification, report evidence and proposed Document changes, then wait for separate acceptance before updating Document. Do not treat Research as a requirement or silently resolve open Evolve alternatives. Follow the project's version-control policy for Research and Evolve; RED does not choose one. Report conflicts between Document and implementation evidence.
+<!-- red:end -->

red_methodology-0.1.0/src/red_cli/bundled/skill/red/assets/RED.md

@@ -0,0 +1,33 @@
+# RED Agent Instructions
+
+This project uses RED Protocol 1 to separate unresolved research, ongoing change, and accepted project knowledge.
+
+## Knowledge states
+
+### Research
+
+Research contains unresolved questions, evidence, hypotheses, experiments, and conflicting claims. Do not treat it as accepted requirements.
+
+### Evolve
+
+Evolve contains proposed or active changes, their rationale, affected areas, acceptance conditions, and open questions. Preserve unresolved alternatives until the user or project policy decides them.
+
+### Document
+
+Document contains accepted project goals, terminology, interfaces, architecture rules, operating instructions, and contribution rules. Treat it as the normative baseline.
+
+Code, tests, configuration, and runtime output provide implementation evidence. Report conflicts with Document and investigate them through Research. A resulting decision may repair the implementation or create an Evolve item that changes Document.
+
+## Workflow
+
+1. Read repository instructions and `red.toml` when present.
+2. Load only the Document, active Evolve, Research, and implementation evidence relevant to the task.
+3. Implement directly when accepted knowledge specifies the work.
+4. Use Research when an unknown can change the decision. Report findings and wait for explicit authority before entering Evolve.
+5. Use Evolve when the task changes accepted behavior, data, public interfaces, architecture, or engineering rules. A clear change may enter Evolve directly.
+6. Design, implement, test, and revise inside the authorized Evolve scope.
+7. When acceptance conditions pass, report evidence and proposed Document changes. Wait for separate acceptance before updating Document.
+8. Persist R or E when work crosses tasks, needs review, presents alternatives, or leaves an unresolved conflict.
+9. Run `red check --json` when the CLI is available.
+
+Prefer the RED CLI for deterministic operations. If it is unavailable, follow the same protocol by hand. CLI promotion records a decision supplied by the user or project; it does not authorize the transition. Follow the project's version-control policy for Research and Evolve; RED does not require tracked files, local files, or an external tracker. Do not reorganize existing documentation or install tools globally without authorization.

red_methodology-0.1.0/src/red_cli/bundled/skill/red/assets/red.toml

@@ -0,0 +1,14 @@
+version = 1
+
+[document]
+paths = ["README.md", "docs/**"]
+
+[research]
+path = "research"
+
+[evolve]
+path = "evolve"
+
+[policy]
+document_requires_approval = true
+report_document_implementation_conflicts = true

red_methodology-0.1.0/src/red_cli/bundled/skill/red/references/adopt.md

@@ -0,0 +1,15 @@
+# Adopt RED
+
+Adopt RED without reorganizing the repository.
+
+1. Inventory existing README files, maintained docs, ADRs, proposals, investigations, issues, and contribution rules.
+2. Propose a mapping for Document, Evolve, and Research. Explain ambiguous locations.
+3. Prefer the RED CLI. Run `red init` only after the task authorizes project setup.
+4. Edit the generated `red.toml` to reflect the accepted mapping.
+5. Run `red check --json`.
+
+Do not migrate old documents or reconstruct historical decisions. Classify current sources and use RED for work from this point forward.
+
+Choose whether the project tracks Research and Evolve files, keeps them local, or uses its issue or pull-request system. Record the choice in repository guidance or ignore rules; RED supplies no default.
+
+For agents without Skill support, use `red instructions install --target AGENTS.md` or `red instructions export --output RED.md`.

red_methodology-0.1.0/src/red_cli/bundled/skill/red/references/artifacts.md

@@ -0,0 +1,69 @@
+# RED artifacts
+
+Use UTF-8 Markdown with TOML front matter delimited by `+++` for Research and Evolve artifacts. Document follows the project's documentation format and the writing guidance below.
+
+## Research
+
+```md
++++
+id = "R-1"
+state = "research"
+status = "open"
+title = "Tag semantics"
+created = "2026-09-05"
++++
+
+# R-1: Tag semantics
+
+## Question
+
+## Evidence
+
+## Unknowns
+```
+
+## Evolve
+
+```md
++++
+id = "E-1"
+state = "evolve"
+status = "open"
+title = "Add tags"
+created = "2026-09-05"
+based_on = ["R-1"]
++++
+
+# E-1: Add tags
+
+## Change
+
+## Rationale
+
+## Acceptance
+
+## Open questions
+```
+
+Create new artifacts with sequential positive integers without leading zeros within each state. Identifiers have no fixed digit width. Accept legacy four-digit, zero-padded identifiers when reading an existing project, and count them during allocation. Filenames start with the identifier and a readable slug. Keep source artifacts in the working environment while their history remains useful.
+
+Version control is project policy. Inspect repository guidance and ignore rules before staging Research or Evolve. A project may track the files, keep them local, or represent shared work in issues or pull requests.
+
+The CLI may validate promotion readiness and record an accepted decision. The agent presents Research findings before Research-to-Evolve promotion and presents Evolve evidence plus proposed Document changes before Evolve-to-Document promotion. It must not invent agreement or rewrite Document content without an authorized decision.
+
+## Write Document for its readers
+
+Document serves people and agents who need accepted project knowledge while using a feature, implementing a change, reviewing behavior, or diagnosing a problem. Assume they arrive through a search or a direct link without the originating conversation.
+
+Before writing, identify the intended reader, the situation that brings them here, and the question or action the page should support. Use those answers to choose the scope and presentation: procedures for performing tasks, contracts and examples for implementing against interfaces, or boundaries and rationale for making design decisions. Fit the existing documentation structure; these are choices, not mandatory sections.
+
+When drafting proposed Document content or applying an accepted change:
+
+1. Lead with the answer the reader needs. Extract the accepted definitions, behavior, rules, boundaries, and necessary rationale, and state them directly. Use descriptive headings and concrete examples where they help the reader act. Update the relevant explanation in place when behavior changes.
+2. Keep working history and unresolved alternatives in R/E. Remove R/E record identifiers, links, citations, provenance footnotes, and narratives about how those records produced the result. This includes optional history or source links. Record any traceability from R/E to the relevant Document paths instead.
+3. Omit authoring dates, last-updated stamps, implementation commit hashes, completion reports, and verification logs from ordinary knowledge pages. Keep delivery evidence in E or version-control history. Include a date, version, or revision only when it changes how the reader interprets or uses the content, or a project-required document format calls for it; explain its role. Examples include an effective date, a supported version range, or an exact revision required for a reproducible procedure. Preserve purposeful metadata in established ADR, release, or audit formats without spreading that format to other pages.
+4. Review the page as its intended reader with R/E, task history, and commit history unavailable. Can they find the answer, understand its scope and rationale, and take the intended action? Remove metadata that does not help those tasks. Fill gaps from accepted knowledge; if a gap needs a new decision, keep it open in E and obtain that decision before presenting it as accepted content.
+
+For example, replace “Implemented retry handling in commit abc123 on 2026-09-11; verification passed” with the accepted contract: “Transient failures are retried up to three times. Authentication failures return immediately.” Add the rationale or usage detail the reader needs. Keep a migration deadline when it determines when the reader must act.
+
+Completion requires both independent readability and absence of references to R/E working records. Existing Document-to-Document organization may be preserved. A document whose subject is RED may explain Research and Evolve as concepts; that does not make a particular working record part of Document.