Core Concepts

curl -X POST http://localhost:7777/api/v1/my-namespace/issues \
  -H "Content-Type: application/json" \
  -d '{
    "title": "Add user authentication",
    "description": "Implement JWT-based authentication for API",
    "status": "open",
    "priority": "P1",
    "tags": ["authentication", "security"],
    "assignee": "alice@example.com"
  }'

# List open issues
curl "http://localhost:7777/api/v1/my-namespace/issues?status=open"

# Filter by priority
curl "http://localhost:7777/api/v1/my-namespace/issues?priority=P0&priority=P1"

# Filter by tags
curl "http://localhost:7777/api/v1/my-namespace/issues?tags=security"

curl -X POST http://localhost:7777/api/v1/my-namespace/decisions \
  -H "Content-Type: application/json" \
  -d '{
    "decision": "Use PostgreSQL for production database",
    "rationale": "Better performance, ACID compliance, rich ecosystem",
    "alternatives": ["MySQL", "MongoDB", "CockroachDB"],
    "consequences": "Requires PostgreSQL hosting, industry-standard choice",
    "status": "accepted",
    "tags": ["architecture", "database"]
  }'

curl -X POST http://localhost:7777/api/v1/my-namespace/work-logs \
  -H "Content-Type: application/json" \
  -d '{
    "date": "2025-11-18",
    "summary": "Implemented user authentication system",
    "tasks_completed": [
      "Added JWT token generation",
      "Created login/logout endpoints",
      "Wrote unit tests for auth flow"
    ],
    "context": "Completed issue #42",
    "hours": 6,
    "tags": ["authentication", "backend"]
  }'

curl -X POST http://localhost:7777/api/v1/my-namespace/architecture \
  -H "Content-Type: application/json" \
  -d '{
    "component_name": "User Authentication Service",
    "layer": "backend",
    "technology": "Node.js with Express",
    "description": "Handles user login, registration, and session management",
    "rationale": "Express provides lightweight routing with JWT for stateless auth",
    "trade_offs": "Requires Redis for session caching, but enables horizontal scaling",
    "dependencies": "PostgreSQL, Redis, jsonwebtoken",
    "tags": ["authentication", "backend", "api"]
  }'

curl -X POST http://localhost:7777/api/v1/my-namespace/best-practices \
  -H "Content-Type: application/json" \
  -d '{
    "key": "api-error-handling",
    "title": "Error Handling in API Endpoints",
    "category": "backend",
    "description": "Always use try-catch blocks in async routes with structured error responses",
    "example": "app.get(\"/api/users\", async (req, res) => { try { const users = await User.findAll(); res.json(users); } catch (err) { logger.error(err); res.status(500).json({ error: err.message }); } })",
    "tags": ["backend", "error-handling", "api"]
  }'

curl -X POST http://localhost:7777/api/v1/my-namespace/patterns \
  -H "Content-Type: application/json" \
  -d '{
    "pattern_name": "Repository Pattern",
    "category": "design",
    "problem": "Direct database access scattered throughout codebase makes testing difficult",
    "solution": "Abstract data access behind repository interfaces for testability",
    "use_cases": "When you need testable, swappable data access layer",
    "example": "class UserRepository { async getById(id) { return db.users.findById(id) } }",
    "pros": "Testability, separation of concerns, easy to swap databases",
    "cons": "Additional abstraction layer, more boilerplate code",
    "tags": ["architecture", "clean-code", "testing"]
  }'

curl -X POST http://localhost:7777/api/v1/tags \
  -H "Content-Type: application/json" \
  -d '{
    "name": "postgresql",
    "display_name": "PostgreSQL",
    "color": "#336791",
    "description": "PostgreSQL database related items"
  }'

# Decision to use PostgreSQL implements Architecture component
curl -X POST http://localhost:7777/api/v1/my-namespace/relationships \
  -H "Content-Type: application/json" \
  -d '{
    "source_type": "decision",
    "source_id": 5,
    "target_type": "architecture",
    "target_id": 12,
    "relationship_type": "implements",
    "metadata": "{\"phase\": \"initial-setup\"}"
  }'

# Get all entities related to decision #5
curl "http://localhost:7777/api/v1/my-namespace/relationships/traverse/decision/5"

curl -X POST http://localhost:7777/api/v1/my-namespace/generic-memories \
  -H "Content-Type: application/json" \
  -d '{
    "title": "PostgreSQL Connection Pooling Guide",
    "content": "Use connection pooling with max_connections=100 and idle_timeout=10min for optimal performance",
    "summary": "Best practices for PostgreSQL connection pooling in production",
    "context": "Discovered during performance optimization sprint",
    "source": "PostgreSQL documentation + internal testing",
    "reference_links": ["https://www.postgresql.org/docs/current/runtime-config-connection.html"],
    "key_takeaways": [
      "Set max_connections based on workload",
      "Monitor pool exhaustion",
      "Use PgBouncer for large-scale deployments"
    ],
    "action_items": ["Configure PgBouncer", "Add monitoring alerts"],
    "importance": "high",
    "category": "database",
    "tags": ["postgresql", "performance", "production"],
    "related_to": {"decision_ids": [42], "architecture_ids": [15]},
    "metadata": {"verified_by": "alice", "last_reviewed": "2025-12-14"}
  }'

curl "http://localhost:7777/api/v1/my-namespace/generic-memories/123"