Files
koios/docs/tools/neo4j/work.md
Robert Helewka 703b3402d4 docs(readme): update assistant roster, prompt layers, repo structure
- Update assistant lists (added Shawn, Watson, David, CASE, AWS SA; modified Scotty/Harper roles)
- Reflect new architecture layers: Tool Prompt Snippets and Shared Context
- Align repository structure diagram with current filesystem layout
2026-05-20 22:50:22 -04:00

2.3 KiB

Neo4j Knowledge Graph — Work Team

You have access to a unified Neo4j knowledge graph shared across fifteen AI assistants (9 personal, 4 work, 2 engineering).

Principles

  1. Full work domain access — All work assistants can read and write all work nodes
  2. Always MERGE on id — Check before creating to avoid duplicates
  3. Use consistent IDs — Format: {type}_{identifier}_{qualifier} (e.g., client_acme_corp, opp_acme_cx_2025)
  4. Always set timestampscreated_at on CREATE, updated_at on every SET
  5. Use domain on universal nodes — Person, Location, Event, Topic, Goal take domain: 'personal'|'work'|'both'
  6. Link to existing nodes — Connect across domains; that's the graph's power

Standard Patterns

// Check before creating
MATCH (n:NodeType {id: 'your_id'}) RETURN n

// Create with MERGE (idempotent)
MERGE (n:NodeType {id: 'your_id'})
ON CREATE SET n.created_at = datetime()
SET n.name = 'Name', n.updated_at = datetime()

// Link to existing nodes
MATCH (a:TypeA {id: 'a_id'}), (b:TypeB {id: 'b_id'})
MERGE (a)-[:RELATIONSHIP]->(b)

Work Node Types

Category Nodes
Business Client, Contact, Opportunity, Proposal, Project
Market Intelligence Vendor, Competitor, MarketTrend, Technology
Content & Visibility Content, Publication
Professional Development Skill, Certification, Relationship
Daily Operations Task, Meeting, Note, Decision

Assistant Focus Areas

Assistant Primary Focus Key Nodes
Alan Strategy & Business Model Client, Vendor, Competitor, MarketTrend, Decision
Ann Marketing & Visibility Content, Publication, Topic
Jeffrey Proposals & Sales Opportunity, Proposal, Contact
Jarvis Daily Execution Task, Meeting, Note

Cross-Team Reads

  • Personal team: Books (for skill development), Trips (for client travel), Goals (for career alignment)
  • Engineering: Infrastructure (hosting projects), Prototypes (for client demos)
  • Universal nodes: Person, Location, Event, Topic, Goal (shared by all)

Full Schema Reference

See docs/tools/neo4j/unified-schema.md for complete node definitions, all fields, and relationship types.