Welcome to redplanethq!
Welcome to redplanethq!
Technology that learns you, not the other way around.
Technology that learns you, not the other way around.
Technology that learns you, not the other way around.
meet core, your digital brain
Core transforms everything—people, events, decisions, and tools—into a living, searchable knowledge graph. It’s more than just storage: Core captures every detail and context, connecting facts, relationships, and expertise so your agents and workflows always have the full picture.
Here’s how Core organizes and empowers your knowledge:
1. Knowledge Graph
Core structures all information as a knowledge graph, using the subject–predicate–object model. Each “fact” is a connection—linking people, projects, events, and concepts as nodes in a network. This approach enables powerful search, relationship mapping, and reasoning:
• Example: “Harshith (person) is founder of (relationship) RedPlanetHQ (organization)”
• Agents and users can instantly traverse connections, surface hidden links, and understand how everything fits together.
2. Not Just Facts: Episodic Memory
Core doesn’t just store isolated facts. Every piece of information is tied to its real-world context—meetings, conversations, decisions, and events. This “episodic memory” approach means:
• Facts are always anchored to when, how, and why they were learned.
• Agents can reconstruct the full story behind any detail, preserving intent and sequence.
• Example: “On Jan 12, 2026, Harshith and Maya discussed API design; decided to use REST over GraphQL.”
3. Fact Aspects
Fact aspects define the types of relationships and properties that can exist in Core. They capture the many ways entities connect and interact, so agents can reason, search, and act with precision. Core’s key fact aspects include:
• Identity: Names, roles, contact info, physical stats (“Harshith’s email is harshithmullapudi@gmail.com”)
• Expertise (Knowledge): Skills, domains, tools (“Harshith knows TypeScript”)
• Belief (Worldview): Values, principles, opinions (“Harshith values open-source”)
• Relationship: Who works with whom, reporting lines, collaborations (“Harshith reports to Maya”)
• Status/Event: Progress, blockers, actions, milestones (“Task 42 is in progress”; “API deployed Jan 12, 2026”)
These aspects let agents answer nuanced questions—“What does Maya know?”, “Who’s blocked on this project?”, “Which tools are in use?”
4. Entity Types
Entity types define the categories of objects within Core’s graph. They ensure every fact is attached to the right kind of “thing” and allow powerful filtering, organization, and discovery. Core’s primary entity types include:
• Person: Individuals (e.g., Harshith Mullapudi)
• Organization: Companies or teams (e.g., RedPlanetHQ)
• Product: Apps, services, business platforms (e.g., Slack, GitHub)
• Technology: Languages, frameworks, infrastructure (e.g., TypeScript, AWS)
• Standard: Protocols, methodologies (e.g., OAuth 2.0, Agile)
• Concept: Topics, domains, communities (e.g., Product Management, AI)
• Event: Meetings, milestones, launches (e.g., “API Launch Jan 2026”)
Entity types enable agents and users to find all relevant objects, structure information, and connect facts to the right context.
Core transforms everything—people, events, decisions, and tools—into a living, searchable knowledge graph. It’s more than just storage: Core captures every detail and context, connecting facts, relationships, and expertise so your agents and workflows always have the full picture.
Here’s how Core organizes and empowers your knowledge:
1. Knowledge Graph
Core structures all information as a knowledge graph, using the subject–predicate–object model. Each “fact” is a connection—linking people, projects, events, and concepts as nodes in a network. This approach enables powerful search, relationship mapping, and reasoning:
• Example: “Harshith (person) is founder of (relationship) RedPlanetHQ (organization)”
• Agents and users can instantly traverse connections, surface hidden links, and understand how everything fits together.
2. Not Just Facts: Episodic Memory
Core doesn’t just store isolated facts. Every piece of information is tied to its real-world context—meetings, conversations, decisions, and events. This “episodic memory” approach means:
• Facts are always anchored to when, how, and why they were learned.
• Agents can reconstruct the full story behind any detail, preserving intent and sequence.
• Example: “On Jan 12, 2026, Harshith and Maya discussed API design; decided to use REST over GraphQL.”
3. Fact Aspects
Fact aspects define the types of relationships and properties that can exist in Core. They capture the many ways entities connect and interact, so agents can reason, search, and act with precision. Core’s key fact aspects include:
• Identity: Names, roles, contact info, physical stats (“Harshith’s email is harshithmullapudi@gmail.com”)
• Expertise (Knowledge): Skills, domains, tools (“Harshith knows TypeScript”)
• Belief (Worldview): Values, principles, opinions (“Harshith values open-source”)
• Relationship: Who works with whom, reporting lines, collaborations (“Harshith reports to Maya”)
• Status/Event: Progress, blockers, actions, milestones (“Task 42 is in progress”; “API deployed Jan 12, 2026”)
These aspects let agents answer nuanced questions—“What does Maya know?”, “Who’s blocked on this project?”, “Which tools are in use?”
4. Entity Types
Entity types define the categories of objects within Core’s graph. They ensure every fact is attached to the right kind of “thing” and allow powerful filtering, organization, and discovery. Core’s primary entity types include:
• Person: Individuals (e.g., Harshith Mullapudi)
• Organization: Companies or teams (e.g., RedPlanetHQ)
• Product: Apps, services, business platforms (e.g., Slack, GitHub)
• Technology: Languages, frameworks, infrastructure (e.g., TypeScript, AWS)
• Standard: Protocols, methodologies (e.g., OAuth 2.0, Agile)
• Concept: Topics, domains, communities (e.g., Product Management, AI)
• Event: Meetings, milestones, launches (e.g., “API Launch Jan 2026”)
Entity types enable agents and users to find all relevant objects, structure information, and connect facts to the right context.
Core transforms everything—people, events, decisions, and tools—into a living, searchable knowledge graph. It’s more than just storage: Core captures every detail and context, connecting facts, relationships, and expertise so your agents and workflows always have the full picture. Here’s how Core organizes and empowers your knowledge:
1. Knowledge Graph
Core structures all information as a knowledge graph, using the subject–predicate–object model. Each “fact” is a connection—linking people, projects, events, and concepts as nodes in a network. This approach enables powerful search, relationship mapping, and reasoning:
• Example: “Harshith (person) is founder of (relationship) RedPlanetHQ (organization)”
• Agents and users can instantly traverse connections, surface hidden links, and understand how everything fits together.
2. Not Just Facts: Episodic Memory
Core doesn’t just store isolated facts. Every piece of information is tied to its real-world context—meetings, conversations, decisions, and events. This “episodic memory” approach means:
• Facts are always anchored to when, how, and why they were learned.
• Agents can reconstruct the full story behind any detail, preserving intent and sequence.
• Example: “On Jan 12, 2026, Harshith and Maya discussed API design; decided to use REST over GraphQL.”
3. Fact Aspects
Fact aspects define the types of relationships and properties that can exist in Core. They capture the many ways entities connect and interact, so agents can reason, search, and act with precision. Core’s key fact aspects include:
• Identity: Names, roles, contact info, physical stats (“Harshith’s email is harshithmullapudi@gmail.com”)
• Expertise (Knowledge): Skills, domains, tools (“Harshith knows TypeScript”)
• Belief (Worldview): Values, principles, opinions (“Harshith values open-source”)
• Relationship: Who works with whom, reporting lines, collaborations (“Harshith reports to Maya”)
• Status/Event: Progress, blockers, actions, milestones (“Task 42 is in progress”; “API deployed Jan 12, 2026”)
These aspects let agents answer nuanced questions—“What does Maya know?”, “Who’s blocked on this project?”, “Which tools are in use?”
4. Entity Types
Entity types define the categories of objects within Core’s graph. They ensure every fact is attached to the right kind of “thing” and allow powerful filtering, organization, and discovery. Core’s primary entity types include:
• Person: Individuals (e.g., Harshith Mullapudi)
• Organization: Companies or teams (e.g., RedPlanetHQ)
• Product: Apps, services, business platforms (e.g., Slack, GitHub)
• Technology: Languages, frameworks, infrastructure (e.g., TypeScript, AWS)
• Standard: Protocols, methodologies (e.g., OAuth 2.0, Agile)
• Concept: Topics, domains, communities (e.g., Product Management, AI)
• Event: Meetings, milestones, launches (e.g., “API Launch Jan 2026”)
Entity types enable agents and users to find all relevant objects, structure information, and connect facts to the right context.
Core transforms everything—people, events, decisions, and tools—into a living, searchable knowledge graph. It’s more than just storage: Core captures every detail and context, connecting facts, relationships, and expertise so your agents and workflows always have the full picture.
Here’s how Core organizes and empowers your knowledge:
1. Knowledge Graph
Core structures all information as a knowledge graph, using the subject–predicate–object model. Each “fact” is a connection—linking people, projects, events, and concepts as nodes in a network. This approach enables powerful search, relationship mapping, and reasoning:
• Example: “Harshith (person) is founder of (relationship) RedPlanetHQ (organization)”
• Agents and users can instantly traverse connections, surface hidden links, and understand how everything fits together.
2. Not Just Facts: Episodic Memory
Core doesn’t just store isolated facts. Every piece of information is tied to its real-world context—meetings, conversations, decisions, and events. This “episodic memory” approach means:
• Facts are always anchored to when, how, and why they were learned.
• Agents can reconstruct the full story behind any detail, preserving intent and sequence.
• Example: “On Jan 12, 2026, Harshith and Maya discussed API design; decided to use REST over GraphQL.”
3. Fact Aspects
Fact aspects define the types of relationships and properties that can exist in Core. They capture the many ways entities connect and interact, so agents can reason, search, and act with precision. Core’s key fact aspects include:
• Identity: Names, roles, contact info, physical stats (“Harshith’s email is harshithmullapudi@gmail.com”)
• Expertise (Knowledge): Skills, domains, tools (“Harshith knows TypeScript”)
• Belief (Worldview): Values, principles, opinions (“Harshith values open-source”)
• Relationship: Who works with whom, reporting lines, collaborations (“Harshith reports to Maya”)
• Status/Event: Progress, blockers, actions, milestones (“Task 42 is in progress”; “API deployed Jan 12, 2026”)
These aspects let agents answer nuanced questions—“What does Maya know?”, “Who’s blocked on this project?”, “Which tools are in use?”
4. Entity Types
Entity types define the categories of objects within Core’s graph. They ensure every fact is attached to the right kind of “thing” and allow powerful filtering, organization, and discovery. Core’s primary entity types include:
• Person: Individuals (e.g., Harshith Mullapudi)
• Organization: Companies or teams (e.g., RedPlanetHQ)
• Product: Apps, services, business platforms (e.g., Slack, GitHub)
• Technology: Languages, frameworks, infrastructure (e.g., TypeScript, AWS)
• Standard: Protocols, methodologies (e.g., OAuth 2.0, Agile)
• Concept: Topics, domains, communities (e.g., Product Management, AI)
• Event: Meetings, milestones, launches (e.g., “API Launch Jan 2026”)
Entity types enable agents and users to find all relevant objects, structure information, and connect facts to the right context.
start building
