The Knowledge Graph of Lumoria

[!NOTE] Status: Content ready · Media: Generated cover and original SVG illustration · Last verified: 2026-09-05
Primary capability: Modeling source-grounded repository relationships

[!TIP] Download this learner kit and use the extraction and setup guide. Keep the original starter untouched.

---
config:
  theme: base
  look: classic
  themeVariables:
    darkMode: false
    background: "#ffffff"
    primaryColor: "#f5f5f5"
    primaryTextColor: "#111111"
    primaryBorderColor: "#555555"
    secondaryColor: "#e0e0e0"
    secondaryTextColor: "#111111"
    secondaryBorderColor: "#666666"
    tertiaryColor: "#bdbdbd"
    tertiaryTextColor: "#111111"
    tertiaryBorderColor: "#444444"
    lineColor: "#444444"
    textColor: "#111111"
    mainBkg: "#f5f5f5"
    nodeBorder: "#555555"
    clusterBkg: "#ffffff"
    clusterBorder: "#999999"
    edgeLabelBackground: "#ffffff"
    actorBkg: "#e0e0e0"
    actorBorder: "#555555"
    actorTextColor: "#111111"
    actorLineColor: "#777777"
    signalColor: "#333333"
    signalTextColor: "#111111"
    labelBoxBkgColor: "#f5f5f5"
    labelBoxBorderColor: "#777777"
    labelTextColor: "#111111"
    loopTextColor: "#111111"
    activationBkgColor: "#bdbdbd"
    activationBorderColor: "#555555"
    noteBkgColor: "#f5f5f5"
    noteTextColor: "#111111"
    noteBorderColor: "#777777"
    attributeBackgroundColorOdd: "#f5f5f5"
    attributeBackgroundColorEven: "#e0e0e0"
---
flowchart LR
    accTitle: The Knowledge Graph of Lumoria capability map
    accDescr: Source-backed edges and a cycle-safe visited set prevent decorative but misleading graphs.
    T["types changed"] --> C["core affected"]
    C --> A["api affected"]
    C --> L["cli affected"]
    A --> D["docs affected"]
    D --> S["Unique sorted impact set"]
    L --> S

Legend. Arrows show change impact, the reverse of the dependency lists supplied to the function.

Explanation. Source-backed edges and a cycle-safe visited set prevent decorative but misleading graphs.

Official references

These official sources are the authority for product behavior and availability. Recheck them when using a different surface or after a product update.

• Run subagents
• Custom agents and handoffs
• Agent sessions

Story

Lumoria’s libraries are linked by luminous threads: imports, calls, tests, owners, requirements, and runtime edges.

The fantasy is a memory aid; the engineering lesson requires observable, reproducible evidence.

Learning objectives

• Interpret graph edges as dependencies and traverse impact in the reverse direction.
• Return a sorted, unique affected set including the starting node.
• Handle cycles and reject unknown nodes without confusing filenames with verified relationships.

Prerequisites

For tools and personal accounts, complete the prerequisites guide. For terminal-only study, follow the extracted-kit CLI route; VS Code-specific evidence remains separate.

Evidence boundary: The fixture validates traversal, not automatic discovery of every real repository dependency.

Estimated session: 45–75 minutes after prerequisites; actual duration varies. Never use production secrets or customer data.

Concept explanation

A repository knowledge graph models files, symbols, tests, services, owners, and requirements with typed edges. Imports are not runtime calls, and co-location is not ownership. Graphs help only when bounded, current, and source-anchored. Generated relationships can become stale, so planning decisions must be confirmed against current files and executable checks.

Concrete use case

If api depends on core and core depends on types, a change to types can affect api. A change to api does not automatically affect its dependency types.

Vocabulary checkpoint

• Role: Ask, Plan, Agent, or a custom agent.
• Harness/surface: the runtime or product surface in which a role operates.
• Target: the selected session destination, such as Local, Copilot, or Cloud where exposed.
• Environment: the folder, worktree, local machine, Codespace, or remote environment.
• Instructions: automatically applied durable context.
• Prompt: a manually invoked task template.
• Skill: reusable expertise loaded when relevant.
• Custom agent: a role with instructions, tools, and optional handoffs.
• MCP: Model Context Protocol.
• Evidence: a path, diff, command result, trace, or review decision.

Ask → Plan → Agent workflow

Ask — investigate

1. Identify the real user outcome and current source of truth.
2. Inspect relevant files, instructions, tools, permissions, and existing checks.
3. Cite concrete paths or platform evidence for every important finding.
4. Record uncertainty and do not infer unavailable capabilities.

Gate: No implementation until the current state and evidence are understood.

Plan — design

1. State scope, non-goals, assumptions, risks, and trust boundaries.
2. Select the minimum role, tools, authority, and environment.
3. Define acceptance criteria, verification commands, review, and reset.
4. Mark any Preview or experimental dependency and provide a fallback.

Gate: Another learner should be able to predict completion from the plan.

Agent — execute

1. Make the smallest reversible change or produce the planned artifact.
2. Use short inspect → change → verify loops.
3. Preserve command output, exit status, diffs, traces, or platform records.
4. Stop when acceptance criteria are met; do not perform unrelated cleanup.

Review — challenge

1. Inspect the complete diff or artifact.
2. Compare each result with the plan and acceptance criteria.
3. Run the narrowest relevant existing check, broadening only when justified.
4. Record limitations and unresolved risks.
5. Score the work with rubric.md.

Guided mission

1. Prepare one isolated copy

1. Download and extract the lumoria-graph kit into a new work-drive directory.
2. Read KIT-START.md at its root. Open starter/ as the VS Code workspace when testing discovery, but run the verifier from the kit root.
3. Inspect starter/graph.js, verify.js before editing.
4. From the extracted kit root, run node verify.js.
5. Record the documented starter rejection. A missing runtime or unrelated crash is not the expected exercise result.

2. Investigate and plan

Copyable baseline command, from the extracted kit root:

node verify.js

In Ask, request a trace of the inspected files and what the verifier actually observes. Challenge any claim about live execution that is not supported by output.

Use this planning prompt:

Specify affectedBy for the provided dependency direction. Include the changed node, visit reverse dependants once, handle cycles and sort the final unique names. Explain an unknown-start error.
Do not implement yet. Identify affected files, the negative case and a safe reset.

3. Implement the reviewed slice

1. Approve only the named starter artifact and necessary focused tests.
2. Ask Agent to implement one slice; inspect proposed commands before execution.
3. Run node verify.js again from the kit root, or node ../verify.js from starter/.
4. Compare the exact result with the checkpoint below and review the complete diff.
5. Record host discovery or live activity separately when available. Do not enable extra services to manufacture a passing result.

[!IMPORTANT] Checkpoint: Changing types reaches all five supplied nodes; changing api reaches api and docs only. The fixture validates traversal, not automatic discovery of every real repository dependency.

4. Prove a check can reject a mistake

Reverse the traversal direction deliberately in the disposable implementation. Confirm the types impact case detects the mistake, then restore it.

Finish with the adventure-specific capability evidence in the rubric, not just the presence of a file.

Intentional failure: The Decorative Constellation

Perform this only in a disposable environment:

Draw relationships from filenames and assumptions without reading sources. Unsupported edges create false confidence and an incorrect change plan.

Recovery

Return to Ask, identify the violated boundary, narrow the plan, remove unnecessary authority or context, and repeat the smallest relevant verification. Document the causal lesson rather than merely stating that the attempt failed.

Independent challenge

Model a feature crossing source, configuration, tests, and an external API, including confidence and verification for every edge.

Constraints:

• Do not copy the guided mission verbatim.
• Do not add tools, permissions, or cloud resources without a stated need.
• Do not claim quality, performance, compatibility, or availability without executed evidence.
• Keep fantasy language subordinate to technical clarity.

Evidence checklist

• Source-grounded Ask findings.
• Approved plan with scope, non-goals, risks, checks, and reset.
• Agent diff or artifact limited to the declared scope.
• Verification output with command, status, or platform record.
• Intentional-failure root cause and recovery.
• Independent challenge result.
• Explicit limitations and feature-status notes.
• Completed rubric.md.

Reset instructions

1. Save your diff, command output and limitations from the disposable kit.
2. Stop only the process or learning session you started. Do not stop other projects.
3. If you initialized Git in the kit, inspect git status --short there and restore only your named exercise files from its local baseline.
4. Otherwise, extract the original ZIP into a new unused directory for another attempt; do not overwrite your current work.
5. Remove only exercise-owned configurations, worktrees or remote resources after reviewing anything worth preserving.

The curriculum source and other projects must remain unchanged. A reset of the copied kit is not a repository-wide hard reset.

Next adventure

The Parallel Trials of Mythos