Location
https://www.kennesaw.edu/ccse/events/computing-showcase/fa25-cday-program.php
Document Type
Event
Start Date
24-11-2025 4:00 PM
Description
Meetless functions as an OS for modern organizations: a secure, multi-agent runtime that turns scattered inputs (docs, emails, tickets, chats) into asynchronous, outcome-driven discussions with decisions, owners, and due dates—so teams ship without meetings. System architecture (OS metaphor).- Kernel (Orchestrator): schedules “processes” across specialized agents using routing policies, guardrails, and retry semantics. - Process I/O: unified connectors for Google/Microsoft suites, Slack, Jira/Linear, and web sources, normalized into a document graph with vector embeddings. - Memory & FS: temporal knowledge graph (Neo4j) + document store (PostgreSQL) + vector index (Weaviate) with time-aware retrieval. - Syscalls/APIs: /discussions.create, /decisions.propose, /actions.sync, /summaries.latest; all idempotent with audit trails. - Runtime & Toolchain: FastAPI services; LangGraph/LangChain for agent flows; MLFlow for experiment tracking; background workers for ingestion, scoring, and SLA enforcement. Workflow. 1. Ingest context: generate a structured Brief (goals, constraints, risks, dependencies).2. Facilitate threaded Q&A; auto-summarize positions and trade-offs. 3. Produce a Decision & Action Pack (decisions, owners, due dates) and sync to PM tools. 4. Update the temporal graph; surface follow-ups and unresolved questions. Security & governance: RBAC with tenant isolation, secret-scoped connectors, redaction/masking policies, and full decision lineage via timeline views. Evaluation targets (pilot teams, n=6): ≥40% reduction in meeting hours for standups/planning/retros; < 5 min median catch-up time for late joiners; measurable increase in decision traceability and follow-up closure rate.
Included in
GC-1144 Meetless: The Operating System for Business in the AI Age
https://www.kennesaw.edu/ccse/events/computing-showcase/fa25-cday-program.php
Meetless functions as an OS for modern organizations: a secure, multi-agent runtime that turns scattered inputs (docs, emails, tickets, chats) into asynchronous, outcome-driven discussions with decisions, owners, and due dates—so teams ship without meetings. System architecture (OS metaphor).- Kernel (Orchestrator): schedules “processes” across specialized agents using routing policies, guardrails, and retry semantics. - Process I/O: unified connectors for Google/Microsoft suites, Slack, Jira/Linear, and web sources, normalized into a document graph with vector embeddings. - Memory & FS: temporal knowledge graph (Neo4j) + document store (PostgreSQL) + vector index (Weaviate) with time-aware retrieval. - Syscalls/APIs: /discussions.create, /decisions.propose, /actions.sync, /summaries.latest; all idempotent with audit trails. - Runtime & Toolchain: FastAPI services; LangGraph/LangChain for agent flows; MLFlow for experiment tracking; background workers for ingestion, scoring, and SLA enforcement. Workflow. 1. Ingest context: generate a structured Brief (goals, constraints, risks, dependencies).2. Facilitate threaded Q&A; auto-summarize positions and trade-offs. 3. Produce a Decision & Action Pack (decisions, owners, due dates) and sync to PM tools. 4. Update the temporal graph; surface follow-ups and unresolved questions. Security & governance: RBAC with tenant isolation, secret-scoped connectors, redaction/masking policies, and full decision lineage via timeline views. Evaluation targets (pilot teams, n=6): ≥40% reduction in meeting hours for standups/planning/retros; < 5 min median catch-up time for late joiners; measurable increase in decision traceability and follow-up closure rate.