# nimic - Doramagic AI Context Pack

> Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated.

## Sufficiency Principle

- **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary.
- **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work.

## How the Host AI Should Use This

You are reading the AI Context Pack that Doramagic compiled for nimic. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project.

## Claim Consumption Rules

- **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure.
- **Minimum status for a fact**: `supported`
- `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path.
- `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying.
- `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact.
- `unverified`: Must not be used as fact; state clearly that evidence is insufficient.
- `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf.

## Who It Fits Best

- **Users who want to understand an open-source project's value and boundaries before installing**: Current evidence comes mainly from project documentation. Evidence: `README.md` Claim: `clm_0002` supported 0.86

## What It Can Do

- **Project Knowledge Preview** (Previewable before install): The project can be read and explained, but current evidence is not enough to confirm installable capabilities or a runtime entrypoint. Evidence: `README.md`, `LICENSE`, `src/nimic/ncode/nimpy/LICENSE`, `nimic_translation_rules.md` et al. Claim: `clm_0001` supported 0.86

## How to Start

- No stable Quick Start command in the project evidence; this should be left empty rather than fabricated by Doramagic.

## Continue-or-Stop Decision Card

- **Current recommendation**: Run Prompt Preview first
- **Why**: There is enough information for a pre-install experience, but real compatibility, output quality, and risk boundaries cannot yet be trusted directly.

### 30-Second Read

- **What to do now**: Run Prompt Preview first
- **Minimum safe next step**: Run Prompt Preview first
- **Do not trust yet**: Real output quality cannot be trusted before install.
- **Continuing will touch**: Host AI context

### What You Can Trust Now

- **Target-audience signal: Users who want to understand an open-source project's value and boundaries before installing** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0002` supported 0.86
- **Capability exists: Project Knowledge Preview** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md`, `LICENSE`, `src/nimic/ncode/nimpy/LICENSE`, `nimic_translation_rules.md` et al. Claim: `clm_0001` supported 0.86

### What You Cannot Trust Yet

- **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project.
- **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment.
- **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior.
- **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first.
- **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment.
- **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.

### What Continuing Will Touch

- **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts.

### Minimum Safe Next Steps

- **Run Prompt Preview first**: Use a pre-install interactive trial to judge whether the way of working fits; it needs no authorization or environment change. (applies when: Applies to any project, especially when output quality is unknown.)
- **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.)

### Exit Plan

- **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable.
- **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck.

## What Can Only Be Previewed

- Explain who the project fits and what it can do
- Demonstrate a typical conversation flow based on project docs
- Help the user decide whether it is worth installing or researching further

## What Must Be Verified After Install

- Actually installing the Skill, plugin, or CLI
- Running scripts, modifying local files, or accessing external services
- Verifying real output quality, performance, and compatibility

## Boundary & Risk Decision Card

- **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0003` inferred 0.45
- **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment.
- **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation.

## Pre-Work Working Context

### Loading Order

- First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset.
- Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative.
- Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match.
- When you need to carry out a concrete task, check role_skill_index first, then evidence_index.
- For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required.

### Task Routes

- **Project Knowledge Preview**: Use role_skill_index / evidence_index to help the user pick a usable role, Skill, or workflow first. Boundary: Can be experienced via a pre-install Prompt. Evidence: `README.md`, `LICENSE`, `src/nimic/ncode/nimpy/LICENSE`, `nimic_translation_rules.md` et al. Claim: `clm_0001` supported 0.86

### Context Scale

- Total files: 41
- Important-file coverage: 23/41
- Evidence index entries: 22
- Role / Skill entries: 2

### Handling Insufficient Evidence

- **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts.
- **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install.
- **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run.
- **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version.

## Prompt Recipes

### Fit assessment

- Goal: Judge whether this project fits the user's current task.
- Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation.

```text
Based on the AI Context Pack for nimic, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id.
```

### Pre-install experience

- Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise.
- Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language.

```text
Treat nimic as a pre-install experience asset, not an already-installed tool or a real runtime environment.

Output exactly four parts:
1. Ask me 3 necessary questions first.
2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow.
3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run.
4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project.

Hard boundaries:
- Do not claim you have installed, run, executed tests, modified files, or produced real results.
- Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing".
- If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...".
- The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating".
- Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment.
- Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions.

```

### Role / Skill selection

- Goal: Pick the best-matching asset from the project's roles or Skills.
- Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed.

```text
Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs.
```

### Risk pre-check

- Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting.
- Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items.

```text
Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have.
```

### Host AI kickoff instruction

- Goal: Turn the project context into a host AI instruction for the start of a conversation.
- Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI.

```text
Based on the AI Context Pack for nimic, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results.
```

## Role / Skill Index

- Indexed 2 role / Skill / project-doc entries.

- **Nimic** (project_doc): Nimic allows using pure Python as a systems language with AOT compilation. It provides systems-level functionality directly within CPython backed by the built-in ctypes module , while allowing the exact same code to compile Ahead-Of-Time AOT to an efficient native binary. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md`
- **Nimic Translation Rules Nim - Python Nimic** (project_doc): Nimic Translation Rules Nim - Python Nimic Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `nimic_translation_rules.md`

## Evidence Index

- Indexed 22 evidence entries.

- **Nimic** (documentation): Nimic allows using pure Python as a systems language with AOT compilation. It provides systems-level functionality directly within CPython backed by the built-in ctypes module , while allowing the exact same code to compile Ahead-Of-Time AOT to an efficient native binary. Evidence: `README.md`
- **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `LICENSE`
- **License** (source_file): Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files the "Software" , to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: Evidence: `src/nimic/ncode/nimpy/LICENSE`
- **Nimic Translation Rules Nim - Python Nimic** (documentation): Nimic Translation Rules Nim - Python Nimic Evidence: `nimic_translation_rules.md`
- **.python-version** (source_file): 3.12 Evidence: `.python-version`
- **Pyproject** (source_file): project name = "nimic" version = "0.0.5" authors = { name = "Dmytro Makogon"} description = "Pure Python module that facilitates writing AOT compilable code" readme = "README.md" license = "MIT" requires-python = " =3.12" dependencies = classifiers = "Topic :: Software Development :: Compilers", "Programming Language :: Python :: 3", Evidence: `pyproject.toml`
- **Convert final Expr/Return to Assign using original targets** (source_file): n templates = {} ⋮---- def template template func ⋮---- is untyped = ⋮---- is untyped = True ⋮---- template source = inspect.getsource template func template source = textwrap.dedent template source template ast = ast.parse template source ⋮---- template def node = template ast.body 0 ⋮---- template body nodes = template def node.body template params = arg.arg for arg in template def node.args.args ⋮---- class ParameterReplacer ast.NodeTransformer ⋮---- def init self, arg map ⋮---- def visit Name self, node ⋮---- class TemplateInliner ast.NodeTransformer ⋮---- def init self, dict with templates ⋮---- def inline call self, call node, targets=None ⋮---- template name = call node.func.id templ… Evidence: `src/nimic/inliner.py`
- **Don't use this** (source_file): import dynlib, macros, os, strutils, typetraits, tables, json, strformat, nimpy/ py types, py utils, nim py marshalling, py nim marshalling Evidence: `src/nimic/ncode/nimpy.nim`
- **Enum handling** (source_file): import std/ json, complex, tables import ./py types, ./py utils import ./py lib as lib Evidence: `src/nimic/ncode/nimpy/nim_py_marshalling.nim`
- **Name the type that is unable to be converted.** (source_file): import std/ json, complex, tables, strutils import ./py types, ./py utils import ./py lib as lib Evidence: `src/nimic/ncode/nimpy/py_nim_marshalling.nim`
- **A type specialized version of ..< for convenience so that** (source_file): type nbool = bool nint = int uintp = uint intp = int Evidence: `src/nimic/ncode/pydefs.nim`
- **presense of comptime in "if" expression forces aot evaluation** (source_file): class untyped ⋮---- SomeInteger = int SomeFloat = float ⋮---- byte = uint8 ⋮---- def u8 x: int - uint8: return uint8 x def u16 x: int - uint16: return uint16 x def u32 x: int - uint32: return uint32 x def u64 x: int - uint64: return uint64 x ⋮---- def i8 x: int - int8: return int8 x def i16 x: int - int16: return int16 x def i32 x: int - int32: return int32 x def i64 x: int - int64: return int64 x ⋮---- def f16 x: float - float16: return float16 x def f32 x: float - float32: return float32 x def f64 x: float - float64: return float64 x ⋮---- def ch x: str - char: return char x ⋮---- const = contextlib.nullcontext let = contextlib.nullcontext var = contextlib.nullcontext block = contextlib.n… Evidence: `src/nimic/ntypes.py`
- **--- Generic Type Classes & Aliases ---** (source_file): class NilPtr ⋮---- slots = ' type name', ⋮---- @property def is nil self - bool ⋮---- def init self, type name: str ⋮---- def bool self - bool ⋮---- def eq self, other - bool ⋮---- def ne self, other - bool ⋮---- def hash self - int ⋮---- def repr self - str ⋮---- resolved = {} ⋮---- dispatch generic = {} ⋮---- dispatch genericT = {} ⋮---- tdefs = {} ⋮---- arg names = {} ⋮---- --- Generic Type Classes & Aliases --- ⋮---- n generic types = { ⋮---- n aliases = {"float": "float64", "int": "int32", "str": "string", "NBool": "bool", ⋮---- def get type params fn: callable - dict ⋮---- lines = ins.getsource fn .split "\n" ⋮---- T str = line line.find " " + 1 : line.find " " .split ", " T def = {}… Evidence: `src/nimic/ntypesystem.py`
- **Algorithm** (source_file): @dispatch def sort s: mut @ seq string Evidence: `src/nimic/std/algorithm.py`
- **Endians** (source_file): def get addr obj ⋮---- def big endian32 dst: pointer, src: pointer ⋮---- src addr = get addr src dst addr = get addr dst ⋮---- val = ctypes.cast src addr, ctypes.POINTER ctypes.c uint32 0 ⋮---- val swapped = struct.unpack ' I', val 0 ⋮---- def little endian32 dst: pointer, src: pointer Evidence: `src/nimic/std/endians.py`
- **Monotimes** (source_file): class MonoTime ⋮---- slots = " ns", ⋮---- def init self, nanoseconds: int ⋮---- def sub self, other: "MonoTime" - Duration ⋮---- def repr self - str ⋮---- def get mono time - MonoTime ⋮---- """Return the current monotonic time Nim: getMonoTime .""" Evidence: `src/nimic/std/monotimes.py`
- **Options** (source_file): class Option ⋮---- def init self, value=None, has value=False ⋮---- def class getitem cls, T ⋮---- type name = T. name if hasattr T, ' name ' else str T specialized = type f"Option {type name} ", Option, , {" n inner type": T} ⋮---- def is some self - bool ⋮---- def is none self - bool ⋮---- def get self ⋮---- def unsafe get self ⋮---- def eq self, other ⋮---- def repr self ⋮---- def str self ⋮---- def bool self ⋮---- """Allow truthiness check: if opt: ... is equivalent to if opt.is some : ... .""" ⋮---- def some value - Option ⋮---- """Create an Option containing a value.""" ⋮---- def none T=None - Option ⋮---- """Create an empty Option. T is the type parameter used for type annotations, i… Evidence: `src/nimic/std/options.py`
- **Os** (source_file): fmRead = "r" ⋮---- fmWrite = "w" ⋮---- fmAppend = "a" ⋮---- fmReadWriteExisting = "r+" ⋮---- fmReadWrite = "w+" ⋮---- def create dir dir: str - None ⋮---- class PathComponent Enum ⋮---- pcFile = "pcFile" pcDir = "pcDir" pcLinkToFile = "pcLinkToFile" pcLinkToDir = "pcLinkToDir" ⋮---- pcFile = PathComponent.pcFile pcDir = PathComponent.pcDir ⋮---- class WalkEntry ⋮---- slots = 'kind', 'path' def init self, kind, path ⋮---- def walk dir path: str ⋮---- def extract filename path: str - str ⋮---- def param count - int ⋮---- def param str i: int - str ⋮---- def get app filename - str ⋮---- def open path: str, mode: str = "r" ⋮---- binary map = {"w": "wb", "a": "ab", "r+": "r+b", "w+": "w+b"} actu… Evidence: `src/nimic/std/os.py`
- **Strutils** (source_file): def int to str i: int, minchars: int = 1 ⋮---- def parse int s: str - int Evidence: `src/nimic/std/strutils.py`
- **Else it should be an int giving the minor version for 3.x.** (source_file): flags = PyCF ONLY AST ⋮---- feature version = -1 ⋮---- feature version = minor Else it should be an int giving the minor version for 3.x. ⋮---- def literal eval node or string ⋮---- """ Evaluate an expression node or a string containing only a Python expression. The string or node provided may only consist of the following Python literal structures: strings, bytes, numbers, tuples, lists, dicts, sets, booleans, and None. Caution: A complex expression can overflow the C stack and cause a crash. """ ⋮---- node or string = parse node or string.lstrip " \t" , mode='eval' ⋮---- node or string = node or string.body def raise malformed node node ⋮---- msg = "malformed node or string" ⋮---- def con… Evidence: `src/nimic/transpiler.py`
- **macOS files** (source_file): Byte-compiled / optimized / DLL files pycache / .py codz $py.class Evidence: `.gitignore`
- **Preprocess** (source_file): def nearest neighbour compute source index scale: float64, out index: nint, input size: nint - nint ⋮---- result = min nint floor float64 out index scale , input size - 1 ⋮---- reverse channels = nint reverse channels ⋮---- inpRawData = cast ptr UncheckedArray uint8 inpRawData ptr outRawData = cast ptr UncheckedArray float32 outRawData ptr ⋮---- scale h = float64 inpH / float64 outH scale w = float64 inpW / float64 outW ⋮---- src h = nearest neighbour compute source index scale=scale h, out index=h, input size=inpH src w = nearest neighbour compute source index scale=scale w, out index=w, input size=inpW ⋮---- inp f32 = float32 inpRawData src h inpW C + src w C + 1 - reverse channels c + re… Evidence: `examples/preprocess.py`

## Rules the Host AI Must Follow

- **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `LICENSE`, `src/nimic/ncode/nimpy/LICENSE`
- **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `LICENSE`, `src/nimic/ncode/nimpy/LICENSE`

## Questions the User Should Answer First

- Which host AI or local environment do you plan to use it in?
- Do you just want to experience the workflow first, or are you ready to actually install?
- What matters most to you: install cost, output quality, or conflicts with your existing rules?

## Acceptance Checks

- Every capability claim can be traced back to a file path in evidence_refs.
- AI_CONTEXT_PACK.md does not package previews as a real run.
- The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes.

---

## Doramagic Context Augmentation

The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints.

## Human Manual Outline

Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph.

Host AI hard rules:
- Do not treat page titles, section order, summaries, or importance values as factual project evidence.
- When explaining the Human Manual outline, state that it is only a reading route or salience signal.
- Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph.

- **Introduction to Nimic**: importance `high`
  - source_paths: README.md, pyproject.toml, .python-version, nimic_translation_rules.md
- **Type System and DSL Conventions**: importance `high`
  - source_paths: src/nimic/ntypes.py, src/nimic/ntypesystem.py, src/nimic/std/options.py, src/nimic/std/strutils.py
- **Transpiler, Inliner, and Nim Code Generation**: importance `high`
  - source_paths: src/nimic/transpiler.py, src/nimic/inliner.py, src/nimic/ncode/pydefs.nim, src/nimic/ncode/nimpy/nimpy.nim, src/nimic/ncode/nimpy/nim_py_marshalling.nim
- **Standard Library Shims, System Modules, and Practical Examples**: importance `medium`
  - source_paths: src/nimic/std/algorithm.py, src/nimic/std/endians.py, src/nimic/std/math.py, src/nimic/std/monotimes.py, src/nimic/std/options.py

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `793472b296658fa519525d125e4c72865c7dd669`
- inspected_files: `README.md`, `pyproject.toml`, `examples/preprocess.py`, `examples/test_preprocess.py`, `src/nimic/__init__.py`, `src/nimic/__main__.py`, `src/nimic/inliner.py`, `src/nimic/nimpy/__init__.py`, `src/nimic/nimpy/py_types.py`, `src/nimic/nimpy/raw_buffers.py`, `src/nimic/nsystem.py`, `src/nimic/ntypes.py`, `src/nimic/ntypesystem.py`, `src/nimic/std/algorithm.py`, `src/nimic/std/endians.py`, `src/nimic/std/math.py`, `src/nimic/std/monotimes.py`, `src/nimic/std/options.py`, `src/nimic/std/os.py`, `src/nimic/std/paths.py`

Host AI hard rules:
- Without repo_clone_verified=true, do not claim that the source code has been read.
- Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts.
- Without quick_start_verified=true, do not claim that the Quick Start path has run successfully.

## Doramagic Pitfall Constraints

These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes.

### Constraint 1: Capability evidence risk requires verification

- Trigger: README/documentation is current enough for a first validation pass.
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: capability.assumptions | https://news.ycombinator.com/item?id=48646239
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 2: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: downstream_validation.risk_items | https://news.ycombinator.com/item?id=48646239
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 3: Security or permission risk requires verification

- Trigger: no_demo
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: risks.scoring_risks | https://news.ycombinator.com/item?id=48646239
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 4: Maintenance risk requires verification

- Trigger: issue_or_pr_quality=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://news.ycombinator.com/item?id=48646239
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.

### Constraint 5: Maintenance risk requires verification

- Trigger: release_recency=unknown。
- Host AI rule: Reproduce the official install and quickstart path in an isolated environment.
- Why it matters: May increase setup, validation, or first-run risk for the user.
- Evidence: evidence.maintainer_signals | https://news.ycombinator.com/item?id=48646239
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.
