agentleFS
Sign inStart free
QubinodeQubinode/qubinode_navigator/.cursor/rules/adr-reference.mdc

qubinode_navigator / rules

Cursor rule1 starsChanged 10 months agoMITView on GitHub

Qubinode Navigator uses ADRs to document architectural decisions. There are 54+ ADRs in docs/adrs/. Each ADR follows this structure: 1. Title: Short descriptive title 2. Status: Proposed, Accepted, Deprecated, Superseded 3. Context: Why this decision is needed 4. Decision: What was decided 5. Consequences: Impact of the decision

The file

Create a free account to mount
Files
adr-reference.mdc
---
globs: ["docs/adrs/**", "**/*.md"]
alwaysApply: false
---

# Architecture Decision Records (ADRs)

## Overview

Qubinode Navigator uses ADRs to document architectural decisions. There are 54+ ADRs in `docs/adrs/`.

## Finding ADRs

```bash
# List all ADRs
ls docs/adrs/*.md

# Search by topic
grep -l -i "topic" docs/adrs/*.md
```

## Key ADRs by Category

### Core Architecture
- **ADR-0001**: Core architecture decisions
- **ADR-0036**: Airflow integration architecture
- **ADR-0043**: Host network access for VM connectivity

### DAG Development (CRITICAL)
- **ADR-0045**: DAG development standards
  - Triple double quotes for bash_command
  - snake_case naming
  - ASCII-only markers
- **ADR-0046**: Validation pipeline & host execution
- **ADR-0047**: qubinode-pipelines integration

### Infrastructure
- **ADR-0050**: Hybrid host-container architecture
- **ADR-0051**: Vault secrets management
- **ADR-0055**: Zero-friction infrastructure services

### AI/RAG
- **ADR-0049**: Multi-agent LLM memory (pgvector + OpenLineage)

### Testing
- **ADR-0056**: AI assistant test strategy overview
- **ADR-0057**: Unit testing standards
- **ADR-0058**: Integration testing approach
- **ADR-0059**: E2E testing strategy

## ADR Format

Each ADR follows this structure:
1. **Title**: Short descriptive title
2. **Status**: Proposed, Accepted, Deprecated, Superseded
3. **Context**: Why this decision is needed
4. **Decision**: What was decided
5. **Consequences**: Impact of the decision

## When to Reference ADRs

- Creating new DAGs → ADR-0045
- Adding VM operations → ADR-0046, ADR-0047
- Modifying services → ADR-0050
- Adding secrets → ADR-0051
- Working with RAG → ADR-0049
- Writing tests → ADR-0056 through ADR-0059

## Creating New ADRs

```bash
# Next ADR number
ls docs/adrs/adr-*.md | tail -1

# Create new ADR
cp docs/adrs/template.md docs/adrs/adr-00XX-title.md
```

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free