cd examples/deep_context
cargo build --release

export PATH="$PATH:$(pwd)/target/release"

cargo install --path .

cd your-project
deep-context init

deep-context capture \
  --title "Migration to Microservices Architecture" \
  --context "Our monolithic application became difficult to scale. Each deployment required coordinating multiple teams. Performance bottlenecks in one module affected the entire system." \
  --decision "Split into microservices: auth, payments, inventory, and notifications" \
  --rationale "Allows independent scaling, faster deployments, and team autonomy. Each service can use the best technology for its needs." \
  --alternative "Keep monolith but use better caching" \
  --alternative "Use serverless functions" \
  --consequence "Increased operational complexity, need for service mesh" \
  --files "src/auth/**" \
  --files "src/payments/**" \
  --tag "architecture" \
  --tag "microservices"

deep-context capture --interactive

# Free-text search
deep-context query "Why did we choose Redis?"

# Tag-based search
deep-context query --tag architecture

# File-based search
deep-context query --file "src/auth/handler.rs"

# Time-based search
deep-context query --since "2024-01-01" --until "2024-06-30"

# Timeline for entire project
deep-context timeline

# Timeline for specific file
deep-context timeline src/auth/handler.rs

# Timeline for specific decision
deep-context timeline --decision "ADR-001"

# Visual timeline (ASCII art)
deep-context timeline --visual

# Export as Markdown
deep-context export --format markdown --output docs/decisions/

# Export as JSON
deep-context export --format json --output knowledge-base.json

# Export as RDF (for semantic analysis)
deep-context export --format rdf --output knowledge.ttl

# Generate decision graph
deep-context export --format graph --output decision-graph.svg

deep-context capture \
  --title "Migration from PostgreSQL to CockroachDB" \
  --context "We need multi-region deployment with strong consistency. PostgreSQL replication is complex and doesn't provide automatic failover." \
  --decision "Migrate to CockroachDB for distributed SQL with automatic sharding and replication" \
  --rationale "CockroachDB provides PostgreSQL compatibility while adding distributed capabilities out of the box. Reduces operational overhead." \
  --alternative "Use PostgreSQL with Patroni for HA" \
  --alternative "Switch to Cassandra with eventual consistency" \
  --consequence "Need to update connection strings and test transaction behavior. Some PostgreSQL-specific features may not work." \
  --files "src/db/**" \
  --files "config/database.yml" \
  --tag "database" \
  --tag "migration" \
  --tag "infrastructure"

deep-context capture \
  --title "REST vs GraphQL for Public API" \
  --context "Need to expose API to third-party developers. REST is familiar but requires multiple endpoints. GraphQL reduces over-fetching but has a learning curve." \
  --decision "Use GraphQL for flexibility and efficiency" \
  --rationale "Clients can request exactly what they need. Single endpoint simplifies versioning. Better developer experience with introspection and documentation." \
  --alternative "RESTful API with HATEOAS" \
  --alternative "gRPC for better performance" \
  --consequence "Need to implement GraphQL schema, resolvers, and query complexity limits. May need to add REST fallback for simple use cases." \
  --files "src/api/graphql/**" \
  --files "schema.graphql" \
  --tag "api" \
  --tag "graphql"

deep-context capture \
  --title "Implementation of End-to-End Encryption" \
  --context "Users are storing sensitive medical data. Compliance with HIPAA requires encryption at rest and in transit. Zero-knowledge architecture requested by enterprise customers." \
  --decision "Implement E2E encryption with client-side key derivation using Argon2" \
  --rationale "Server never sees plaintext data. Even in case of breach, data remains encrypted. Meets regulatory requirements." \
  --alternative "Server-side encryption with KMS" \
  --alternative "Client-side encryption with server key escrow" \
  --consequence "Cannot implement server-side search. Recovery process more complex. Need to educate users about key management." \
  --files "src/crypto/**" \
  --files "src/auth/key_derivation.rs" \
  --tag "security" \
  --tag "encryption" \
  --tag "compliance"

cargo build --features ai

deep-context query --semantic "How do we handle user authentication?"
# Finds decisions about OAuth, JWT, session management, etc.

git commit -m "Implement JWT refresh tokens

Relates-To: ADR-042
Context: https://deep-context/decisions/ADR-042"

deep-context template create --name security-decision \
  --template .deep-context/templates/security.toml

deep-context graph query "
  SELECT ?decision ?title ?date
  WHERE {
    ?decision dc:type 'ArchitecturalDecision' .
    ?decision dc:title ?title .
    ?decision dc:date ?date .
    ?decision dc:affects <file://src/auth/handler.rs> .
  }
  ORDER BY DESC(?date)
"