# graphrefly-py - 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 graphrefly-py. 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

- **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0001` supported 0.86

## How to Start

- `pip install graphrefly` Evidence: `README.md` Claim: `clm_0003` supported 0.86, `clm_0004` supported 0.86
- `pip install "graphrefly[async]"` Evidence: `README.md` Claim: `clm_0004` supported 0.86

## Continue-or-Stop Decision Card

- **Current recommendation**: Trial role matching first
- **Why**: This project is more of a role library; the core risk is picking the wrong role or treating role copy as execution capability. Trial role matching with Prompt Preview first, then decide whether to sandbox-import it.

### 30-Second Read

- **What to do now**: Trial role matching first
- **Minimum safe next step**: Trial role matching with Prompt Preview first; import in isolation only once satisfied
- **Do not trust yet**: Role quality and task fit cannot be trusted directly.
- **Continuing will touch**: Role selection bias, Command execution, Host AI configuration

### 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: Command-Line Startup or Install Flow** (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` Claim: `clm_0001` supported 0.86
- **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0003` supported 0.86, `clm_0004` supported 0.86

### What You Cannot Trust Yet

- **Role quality and task fit cannot be trusted directly.** (unverified): A role library proves there are many roles; it does not prove each one fits your specific task or that a role produces high-quality results.
- **Do not treat role copy as real execution capability.** (unverified): Before install you can only judge whether the role description and task profile match; you cannot prove it can complete the task inside the host AI.
- **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. Evidence: `AGENTS.md`
- **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

- **Role selection bias**: The user's judgment about which expert role should handle the task. Why: Picking the wrong role makes the AI answer from the wrong expert perspective, wasting time or misleading decisions.
- **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md`
- **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `AGENTS.md`
- **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `README.md`
- **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 an interactive trial to verify the task profile and role match first; do not import the whole role library up front. (applies when: Applies to any project, especially when output quality is unknown.)
- **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.)
- **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.)
- **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.
- **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state.
- **Keep a record of the original role selection**: If output goes off-topic, you can return to the task-profiling stage and reselect a role instead of pushing on with the wrong one.
- **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually.
- **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_0005` inferred 0.45
- **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0006` supported 0.86
- **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.
- **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments.

## 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

- **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0001` supported 0.86

### Context Scale

- Total files: 118
- Important-file coverage: 40/118
- Evidence index entries: 80
- Role / Skill entries: 78

### 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 graphrefly-py, 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 graphrefly-py 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 graphrefly-py, 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 78 role / Skill / project-doc entries.

- **GraphReFly Python** (project_doc): graphrefly is the Python host package for GraphReFly: a reactive graph runtime with a Python-owned facade over the native Rust engine. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `README.md`
- **graphrefly-py -- agent context Python host package** (project_doc): graphrefly-py -- agent context Python host package Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `AGENTS.md`
- **anyio runner** (project_doc): Return a convenience runner for a caller-owned AnyIO task group. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/anyio_runner.md`
- **asyncio runner** (project_doc): Return a convenience runner for a caller-owned asyncio event loop. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/asyncio_runner.md`
- **AsyncRunner** (project_doc): Framework-neutral async job runner supplied explicitly by the host. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/asyncrunner.md`
- **Ctx** (project_doc): Python-owned facade for an advanced node callback invocation. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/ctx.md`
- **from awaitable** (project_doc): Create a source from a fresh awaitable produced on each activation. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/from_awaitable.md`
- **Graph** (project_doc): Graph-first authoring facade over the native Rust engine. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/graph.md`
- **GraphCheckpoint** (project_doc): Generated API reference for graphrefly.GraphCheckpoint. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/graphcheckpoint.md`
- **restore graph** (project_doc): Construct a fresh graph from an already-loaded strict-JSON checkpoint. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/restore_graph.md`
- **trio runner** (project_doc): Return a convenience runner for a caller-owned Trio nursery. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/trio_runner.md`
- **wire bridge** (project_doc): Create a graph-owned high-level wire bridge facade. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wire_bridge.md`
- **wire bridge ack driver** (project_doc): Attach a clock-driven ack timeout driver to a bridge. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wire_bridge_ack_driver.md`
- **wire bridge protobuf** (project_doc): Attach protobuf byte transport nodes to a wire bridge. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wire_bridge_protobuf.md`
- **wire edge group** (project_doc): Attach inbound or outbound wire edge grouping to a bridge. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wire_edge_group.md`
- **API Reference** (project_doc): This page is generated by the Starlight API generator from exported Python package docstrings. Update the public API docstrings in src/graphrefly/ and rebuild with cd website && pnpm build ; do not edit generated website/src/content/docs/api/ output by hand. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/api.md`
- **GraphReFly Python** (project_doc): graphrefly is the Python host package for GraphReFly. It provides a Python facade over the native Rust graph engine and keeps the clean-slate wave protocol inside the native runtime. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/index.md`
- **Quick Start** (project_doc): These examples use the public Python facade over the native Rust graph engine. They intentionally avoid raw native handles, raw protocol ingress, and retired pure-Python runtime surfaces. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/quickstart.md`
- **Release** (project_doc): GraphReFly Python is built with maturin over the native Rust binding crate. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `docs/release.md`
- **version** (project_doc): Generated API reference for graphrefly. version . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/__version__.md`
- **async node** (project_doc): Create a value-level async compute node over declared dependencies. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/async_node.md`
- **CallbackError** (project_doc): A Python callback failed and is mapped into graph ERROR. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/callbackerror.md`
- **ControlMessage** (project_doc): Non-DATA / non-ERROR observation. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/controlmessage.md`
- **DataIssue** (project_doc): Reserved DATA payload for domain/material issues, not protocol ERROR. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/dataissue.md`
- **DataMessage** (project_doc): DATA observation with a domain payload. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/datamessage.md`
- **ErrorMessage** (project_doc): ERROR observation with a Python-owned error envelope. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/errormessage.md`
- **from async iter** (project_doc): Create a source from a fresh async iterable produced on each activation. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/from_async_iter.md`
- **from http** (project_doc): Create a source from one host-supplied HTTP request driver call. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/from_http.md`
- **from sse** (project_doc): Create an SSE source over a host-supplied HTTP byte-stream driver. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/from_sse.md`
- **GraphCallbackError** (project_doc): Callback failure represented as a graph ERROR payload. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/graphcallbackerror.md`
- **GraphEvent** (project_doc): Graph-level observation from the native engine. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/graphevent.md`
- **GraphReentryQueue** (project_doc): Owner-thread drain gate for GraphReFly-owned async completions. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/graphreentryqueue.md`
- **GraphReflyCheckpointError** (project_doc): Checkpoint material is not restorable strict JSON. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/graphreflycheckpointerror.md`
- **GraphReflyError** (project_doc): Base class for public Python facade errors. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/graphreflyerror.md`
- **GraphReflyNoDataError** (project_doc): A node has no cached DATA value at the public Python boundary. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/graphreflynodataerror.md`
- **GraphReflyRestoreError** (project_doc): A checkpoint restore failed honestly at the graph boundary. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/graphreflyrestoreerror.md`
- **GraphReflyRuntimeError** (project_doc): Runtime boundary failure from the native graph engine or host facade. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/graphreflyruntimeerror.md`
- **GraphReflyValueError** (project_doc): Invalid public API value for this facade slice. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/graphreflyvalueerror.md`
- **HttpRequest** (project_doc): Host-driver HTTP request material for Python network source adapters. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/httprequest.md`
- **HttpResponse** (project_doc): Host-driver HTTP response material emitted by from http . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/httpresponse.md`
- **HttpStreamChunkEvent** (project_doc): Streaming driver event carrying a bytes chunk. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/httpstreamchunkevent.md`
- **HttpStreamCompleteEvent** (project_doc): Streaming driver event marking normal stream completion. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/httpstreamcompleteevent.md`
- **HttpStreamDriverEvent** (project_doc): Generated API reference for graphrefly.HttpStreamDriverEvent. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/httpstreamdriverevent.md`
- **HttpStreamErrorEvent** (project_doc): Streaming driver event carrying a host-side stream error. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/httpstreamerrorevent.md`
- **HttpStreamHead** (project_doc): HTTP response head material for streaming source drivers. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/httpstreamhead.md`
- **HttpStreamHeadEvent** (project_doc): Streaming driver event carrying the HTTP response head. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/httpstreamheadevent.md`
- **API Reference** (project_doc): Generated graphrefly Python API reference. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/index.md`
- **LocalHttpDriver** (project_doc): Host-owned one-shot HTTP driver used by from http . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/localhttpdriver.md`
- **LocalHttpStreamDriver** (project_doc): Host-owned streaming HTTP driver used by from sse . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/localhttpstreamdriver.md`
- **Message** (project_doc): Generated API reference for graphrefly.Message. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/message.md`
- **Node** (project_doc): A typed Python handle around an opaque native node. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/node.md`
- **PullContext** (project_doc): Read-only PULL demand context visible during a pull-holder invocation. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/pullcontext.md`
- **restore ref** (project_doc): Return strict-JSON factory metadata for a restorable function-backed node. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/restore_ref.md`
- **restore registry** (project_doc): Build an explicit restore registry for restore graph . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/restore_registry.md`
- **RestoreContext** (project_doc): Descriptor construction context with no raw Node/Ctx/native handles. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/restorecontext.md`
- **RestoreDescriptor** (project_doc): A factory-name restore descriptor used by restore graph . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/restoredescriptor.md`
- **RestoreRef** (project_doc): Factory reference metadata recorded into a strict-JSON checkpoint. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/restoreref.md`
- **RestoreRegistry** (project_doc): Generated API reference for graphrefly.RestoreRegistry. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/restoreregistry.md`
- **Retain** (project_doc): Graph-owned activation root release token. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/retain.md`
- **RewireNext** (project_doc): Callback-scoped deferred topology mutation facade. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/rewirenext.md`
- **SENTINEL** (project_doc): Generated API reference for graphrefly.SENTINEL. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/sentinel-attribute.md`
- **Sentinel** (project_doc): Python representation of protocol SENTINEL in raw ctx wave data. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/sentinel-class.md`
- **SseEvent** (project_doc): Parsed server-sent event DATA emitted by from sse . Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/sseevent.md`
- **SubscriberCallbackError** (project_doc): A subscribe/observe callback failed at the Python observer boundary. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/subscribercallbackerror.md`
- **Subscription** (project_doc): Idempotent subscription handle returned by observe and subscribe calls. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/subscription.md`
- **version** (project_doc): Return the installed Python package version. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/version.md`
- **WireBridge** (project_doc): Graph-owned wire bridge bundle with status and issue nodes. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wirebridge.md`
- **WireBridgeAckDriver** (project_doc): Clock-driven ack timeout driver facade for a wire bridge. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wirebridgeackdriver.md`
- **WireBridgeAckDriverIssue** (project_doc): Graph-visible issue DATA emitted by the bridge ack driver. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wirebridgeackdriverissue.md`
- **WireBridgeAckDriverStatus** (project_doc): Graph-visible status DATA for the bridge ack driver. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wirebridgeackdriverstatus.md`
- **WireBridgeAckTimeout** (project_doc): Graph-visible ack timeout fact emitted by the ack driver. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wirebridgeacktimeout.md`
- **WireBridgeIssue** (project_doc): Graph-visible issue DATA emitted by a wire bridge facade. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wirebridgeissue.md`
- **WireBridgeProtobuf** (project_doc): High-level protobuf byte transport facade for a wire bridge. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wirebridgeprotobuf.md`
- **WireBridgeProtobufIssue** (project_doc): Graph-visible protobuf validation issue DATA. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wirebridgeprotobufissue.md`
- **WireBridgeProtobufStatus** (project_doc): Graph-visible validation status for protobuf byte transport. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wirebridgeprotobufstatus.md`
- **WireBridgeStatus** (project_doc): Graph-visible status DATA for a high-level wire bridge facade. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wirebridgestatus.md`
- **WireEdgeGroup** (project_doc): High-level wire edge group facade for inbound or outbound edge facts. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wireedgegroup.md`
- **WireEdgeGroupIssue** (project_doc): Graph-visible issue DATA emitted by a wire edge group. Activation hint: Reference this when the user needs to understand the project's structure, install path, or boundaries. Evidence: `website/src/content/docs/api/wireedgegroupissue.md`

## Evidence Index

- Indexed 80 evidence entries.

- **GraphReFly Python** (documentation): graphrefly is the Python host package for GraphReFly: a reactive graph runtime with a Python-owned facade over the native Rust engine. Evidence: `README.md`
- **graphrefly-py -- agent context Python host package** (documentation): graphrefly-py -- agent context Python host package Evidence: `AGENTS.md`
- **anyio runner** (documentation): Source: src/graphrefly/ facade.py:3561 Evidence: `website/src/content/docs/api/anyio_runner.md`
- **asyncio runner** (documentation): Source: src/graphrefly/ facade.py:3540 Evidence: `website/src/content/docs/api/asyncio_runner.md`
- **AsyncRunner** (documentation): Source: src/graphrefly/ facade.py:294 Evidence: `website/src/content/docs/api/asyncrunner.md`
- **Ctx** (documentation): Source: src/graphrefly/ facade.py:1569 Evidence: `website/src/content/docs/api/ctx.md`
- **from awaitable** (documentation): Source: src/graphrefly/ facade.py:3121 Evidence: `website/src/content/docs/api/from_awaitable.md`
- **Graph** (documentation): Source: src/graphrefly/ facade.py:2589 Evidence: `website/src/content/docs/api/graph.md`
- **GraphCheckpoint** (documentation): Source: src/graphrefly/ facade.py:95 Evidence: `website/src/content/docs/api/graphcheckpoint.md`
- **restore graph** (documentation): Source: src/graphrefly/ facade.py:3710 Evidence: `website/src/content/docs/api/restore_graph.md`
- **trio runner** (documentation): Source: src/graphrefly/ facade.py:3546 Evidence: `website/src/content/docs/api/trio_runner.md`
- **wire bridge** (documentation): Source: src/graphrefly/ facade.py:3585 Evidence: `website/src/content/docs/api/wire_bridge.md`
- **wire bridge ack driver** (documentation): Source: src/graphrefly/ facade.py:3656 Evidence: `website/src/content/docs/api/wire_bridge_ack_driver.md`
- **wire bridge protobuf** (documentation): Source: src/graphrefly/ facade.py:3597 Evidence: `website/src/content/docs/api/wire_bridge_protobuf.md`
- **wire edge group** (documentation): Source: src/graphrefly/ facade.py:3615 Evidence: `website/src/content/docs/api/wire_edge_group.md`
- **Package** (package_manifest): { "name": "@graphrefly/py-docs-site", "private": true, "type": "module", "packageManager": "pnpm@11.7.0", "scripts": { "docs:gen": "cd .. && uv run python website/scripts/gen-api-docs.py", "docs:gen:check": "cd .. && uv run python website/scripts/gen-api-docs.py --check", "build:starlight-artifact": "pnpm docs:gen && astro build && node scripts/postbuild-python-starlight-artifact.mjs", "build:py-artifact": "pnpm build:starlight-artifact", "predev": "pnpm docs:gen", "dev": "astro dev", "start": "astro dev", "build": "pnpm build:starlight-artifact", "preview": "astro preview" }, "dependencies": { "@astrojs/starlight": "^0.37.2", "astro": "^5.16.0", "sharp": "^0.34.5", "starlight-blog": "^0.25… Evidence: `website/package.json`
- **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`
- **API Reference** (documentation): This page is generated by the Starlight API generator from exported Python package docstrings. Update the public API docstrings in src/graphrefly/ and rebuild with cd website && pnpm build ; do not edit generated website/src/content/docs/api/ output by hand. Evidence: `docs/api.md`
- **GraphReFly Python** (documentation): graphrefly is the Python host package for GraphReFly. It provides a Python facade over the native Rust graph engine and keeps the clean-slate wave protocol inside the native runtime. Evidence: `docs/index.md`
- **Quick Start** (documentation): These examples use the public Python facade over the native Rust graph engine. They intentionally avoid raw native handles, raw protocol ingress, and retired pure-Python runtime surfaces. Evidence: `docs/quickstart.md`
- **Release** (documentation): GraphReFly Python is built with maturin over the native Rust binding crate. Evidence: `docs/release.md`
- **version** (documentation): Source: src/graphrefly/ init .py:155 Evidence: `website/src/content/docs/api/__version__.md`
- **async node** (documentation): Source: src/graphrefly/ facade.py:3460 Evidence: `website/src/content/docs/api/async_node.md`
- **CallbackError** (documentation): Source: src/graphrefly/exceptions.py:28 Evidence: `website/src/content/docs/api/callbackerror.md`
- **ControlMessage** (documentation): Source: src/graphrefly/ facade.py:80 Evidence: `website/src/content/docs/api/controlmessage.md`
- **DataIssue** (documentation): Reserved DATA payload for domain/material issues, not protocol ERROR. Evidence: `website/src/content/docs/api/dataissue.md`
- **DataMessage** (documentation): Source: src/graphrefly/ facade.py:60 Evidence: `website/src/content/docs/api/datamessage.md`
- **ErrorMessage** (documentation): Source: src/graphrefly/ facade.py:72 Evidence: `website/src/content/docs/api/errormessage.md`
- **from async iter** (documentation): Source: src/graphrefly/ facade.py:3186 Evidence: `website/src/content/docs/api/from_async_iter.md`
- **from http** (documentation): Source: src/graphrefly/ facade.py:3254 Evidence: `website/src/content/docs/api/from_http.md`
- **from sse** (documentation): Source: src/graphrefly/ facade.py:3331 Evidence: `website/src/content/docs/api/from_sse.md`
- **GraphCallbackError** (documentation): Source: src/graphrefly/exceptions.py:32 Evidence: `website/src/content/docs/api/graphcallbackerror.md`
- **GraphEvent** (documentation): Source: src/graphrefly/ facade.py:743 Evidence: `website/src/content/docs/api/graphevent.md`
- **GraphReentryQueue** (documentation): Source: src/graphrefly/ facade.py:761 Evidence: `website/src/content/docs/api/graphreentryqueue.md`
- **GraphReflyCheckpointError** (documentation): Source: src/graphrefly/exceptions.py:20 Evidence: `website/src/content/docs/api/graphreflycheckpointerror.md`
- **GraphReflyError** (documentation): Source: src/graphrefly/exceptions.py:4 Evidence: `website/src/content/docs/api/graphreflyerror.md`
- **GraphReflyNoDataError** (documentation): Source: src/graphrefly/exceptions.py:16 Evidence: `website/src/content/docs/api/graphreflynodataerror.md`
- **GraphReflyRestoreError** (documentation): Source: src/graphrefly/exceptions.py:24 Evidence: `website/src/content/docs/api/graphreflyrestoreerror.md`
- **GraphReflyRuntimeError** (documentation): Source: src/graphrefly/exceptions.py:8 Evidence: `website/src/content/docs/api/graphreflyruntimeerror.md`
- **GraphReflyValueError** (documentation): Source: src/graphrefly/exceptions.py:12 Evidence: `website/src/content/docs/api/graphreflyvalueerror.md`
- **HttpRequest** (documentation): Source: src/graphrefly/ facade.py:99 Evidence: `website/src/content/docs/api/httprequest.md`
- **HttpResponse** (documentation): Source: src/graphrefly/ facade.py:109 Evidence: `website/src/content/docs/api/httpresponse.md`
- **HttpStreamChunkEvent** (documentation): Source: src/graphrefly/ facade.py:134 Evidence: `website/src/content/docs/api/httpstreamchunkevent.md`
- **HttpStreamCompleteEvent** (documentation): Source: src/graphrefly/ facade.py:150 Evidence: `website/src/content/docs/api/httpstreamcompleteevent.md`
- **HttpStreamDriverEvent** (documentation): Source: src/graphrefly/ facade.py:168 Evidence: `website/src/content/docs/api/httpstreamdriverevent.md`
- **HttpStreamErrorEvent** (documentation): Source: src/graphrefly/ facade.py:142 Evidence: `website/src/content/docs/api/httpstreamerrorevent.md`
- **HttpStreamHead** (documentation): Source: src/graphrefly/ facade.py:118 Evidence: `website/src/content/docs/api/httpstreamhead.md`
- **HttpStreamHeadEvent** (documentation): Source: src/graphrefly/ facade.py:126 Evidence: `website/src/content/docs/api/httpstreamheadevent.md`
- **API Reference** (documentation): These pages are generated from graphrefly. all and source docstrings through griffe . Update Python docstrings or exports, then rerun pnpm --dir website docs:gen . Evidence: `website/src/content/docs/api/index.md`
- **LocalHttpDriver** (documentation): Source: src/graphrefly/ facade.py:176 Evidence: `website/src/content/docs/api/localhttpdriver.md`
- **LocalHttpStreamDriver** (documentation): Source: src/graphrefly/ facade.py:184 Evidence: `website/src/content/docs/api/localhttpstreamdriver.md`
- **Message** (documentation): Source: src/graphrefly/ facade.py:88 Evidence: `website/src/content/docs/api/message.md`
- **Node** (documentation): Source: src/graphrefly/ facade.py:1928 Evidence: `website/src/content/docs/api/node.md`
- **PullContext** (documentation): Source: src/graphrefly/ facade.py:753 Evidence: `website/src/content/docs/api/pullcontext.md`
- **restore ref** (documentation): Source: src/graphrefly/ facade.py:3679 Evidence: `website/src/content/docs/api/restore_ref.md`
- **restore registry** (documentation): Source: src/graphrefly/ facade.py:3697 Evidence: `website/src/content/docs/api/restore_registry.md`
- **RestoreContext** (documentation): Source: src/graphrefly/ facade.py:311 Evidence: `website/src/content/docs/api/restorecontext.md`
- **RestoreDescriptor** (documentation): Source: src/graphrefly/ facade.py:357 Evidence: `website/src/content/docs/api/restoredescriptor.md`
- **RestoreRef** (documentation): Source: src/graphrefly/ facade.py:302 Evidence: `website/src/content/docs/api/restoreref.md`
- **RestoreRegistry** (documentation): Source: src/graphrefly/ facade.py:96 Evidence: `website/src/content/docs/api/restoreregistry.md`
- The remaining 20 evidence entries are in `AI_CONTEXT_PACK.json` or `EVIDENCE_INDEX.json`.

## 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`, `AGENTS.md`, `website/src/content/docs/api/anyio_runner.md`
- **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`, `AGENTS.md`, `website/src/content/docs/api/anyio_runner.md`

## 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.

- **Overview and System Architecture**: importance `high`
  - source_paths: README.md, src/graphrefly/__init__.py, src/graphrefly/_facade.py, src/graphrefly/_native.pyi, src/graphrefly/_conformance.py
- **Core Graph Programming Model**: importance `high`
  - source_paths: src/graphrefly/__init__.py, src/graphrefly/_facade.py, src/graphrefly/exceptions.py, src/graphrefly/issues.py, website/src/content/docs/api/graph.md
- **Async Boundary and Network Integrations**: importance `high`
  - source_paths: src/graphrefly/__init__.py, website/src/content/docs/api/asyncrunner.md, website/src/content/docs/api/asyncio_runner.md, website/src/content/docs/api/trio_runner.md, website/src/content/docs/api/anyio_runner.md
- **Wire Bridge, Checkpointing, and Operations**: importance `medium`
  - source_paths: src/graphrefly/__init__.py, website/src/content/docs/api/wire_bridge.md, website/src/content/docs/api/wire_bridge_protobuf.md, website/src/content/docs/api/wire_edge_group.md, website/src/content/docs/api/wire_bridge_ack_driver.md

## Repo Inspection Evidence

- repo_clone_verified: true
- repo_inspection_verified: true
- repo_commit: `d21410664880111f7632d3fe7373c06768327485`
- inspected_files: `README.md`, `pyproject.toml`, `docs/api.md`, `docs/index.md`, `docs/quickstart.md`, `docs/release.md`, `src/graphrefly/__init__.py`, `src/graphrefly/_conformance.py`, `src/graphrefly/_facade.py`, `src/graphrefly/exceptions.py`, `src/graphrefly/issues.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://github.com/graphrefly/graphrefly-py
- 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://github.com/graphrefly/graphrefly-py
- 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://github.com/graphrefly/graphrefly-py
- 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://github.com/graphrefly/graphrefly-py
- 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://github.com/graphrefly/graphrefly-py
- Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.