| 23998ae8d64d18f5… | The IP_PATENTS set should be accessible to Leadership and Engineering because intellectual property strategy is confidential. | active | contextual | yes | |
| c4f7d280c0911cf6… | The FINANCIAL_OPS set should be restricted to Leadership only because financial data is sensitive. | active | contextual | yes | |
| 3cb58f7c20a63420… | CLIENTS:* set categories should be accessible only to assigned team members because client data must be handled on a need-to-know basis. | active | contextual | yes | |
| e6c93b7677f95b5f… | The COMPANY_POLICIES set should be accessible to all team members because company policies apply to everyone in the organization. | active | contextual | yes | |
| 5fe4ceb01c642edf… | The CONTRACT_STANDARDS executed contracts set should be restricted to Leadership and Legal because executed contracts may contain negotiated terms. | active | contextual | yes | |
| 9acd9e7d4c783a70… | The CONTRACT_STANDARDS templates set should be accessible to all team members because contract templates are reusable across internal work. | active | contextual | yes | |
| 17fb2e7c4adf78ff… | The deployment is single-tenant for Zeroth Agents internal use, but the knowledge graph should still enforce access scoping across set categories so that information access remains controlled by sensitivity and need-to-know. | active | contextual | yes | |
| 0bb48bdeac78e999… | Client-specific sets should be accessible only to assigned team members because client data is governed by need-to-know access. | active | contextual | yes | |
| 17516c9dc67d9513… | Company policies should be accessible to all team members because those policies apply to everyone in the organization. | active | contextual | yes | |
| a8b5a34542cac91b… | Executed contract standards should be accessible only to Leadership and Legal because executed contracts may contain negotiated terms. | active | contextual | yes | |
| d4a6614b113e4637… | Contract standard templates should be accessible to all team members because templates are reusable across the organization. | active | contextual | yes | |
| c098816aadcb5c5a… | The deployment is single-tenant for Zeroth Agents internal use only, but the knowledge graph should still enforce access scoping so that internal data remains appropriately restricted. | active | contextual | yes | |
| a14edfc8b175bd7e… | The LearningAgent should enable TEMPR memory to learn which CXUs are most frequently retrieved together, such as MSA terms and SLA commitments for proposal generation. | active | contextual | yes | |
| 969c72a954a67c64… | Market estimates and projections should initialize CONTEXT_FOR edges at Q-value 0.45 because they are inherently uncertain. | active | contextual | yes | |
| 8dddb0d6522220cf… | Meeting transcripts should initialize CONTEXT_FOR edges at Q-value 0.55 because they are raw records that may contain misinformation. | active | contextual | yes | |
| 3399979b6c118e42… | Draft documents should initialize CONTEXT_FOR edges at Q-value 0.60 because they may contain unvalidated content. | active | contextual | yes | |
| 5a8ecd7b4705f1ea… | Final-version presentations should initialize CONTEXT_FOR edges at Q-value 0.80 because they have been reviewed and presented. | active | contextual | yes | |
| 0d1138bfc10aea5e… | Contract templates should initialize CONTEXT_FOR edges at Q-value 0.85 because they are approved documents that have not yet been executed. | active | contextual | yes | |
| 054acbf9509d2ac7… | Signed contracts such as MSAs and SOWs should initialize CONTEXT_FOR edges at Q-value 0.90 because they are executed legal documents. | active | contextual | yes | |
| 2caf06b44b829230… | GitHub CLAUDE.md files should initialize CONTEXT_FOR edges at Q-value 0.95 because they are treated as authoritative, maintained documentation. | active | contextual | yes | |
| 5321a01e1a6a4594… | Initial Q-values for CONTEXT_FOR edges must be set based on source reliability so that edge confidence reflects the trustworthiness of each document source type. | active | contextual | yes | |
| 7999287fdfe115fa… | Strategy 3 Text2Cypher should start with lower weight and increase as the graph matures because it handles open-ended queries such as lessons learned and positioning evolution. | active | contextual | yes | |
| 5ba0a734d1dd8d88… | Strategy 2 Edge-filter Cypher should receive medium weight because it is useful for relationship-heavy queries such as client-project filtering and platform reference tracing. | active | contextual | yes | |
| 5ab3c090c344c4bb… | Strategy 1 Template Cypher should receive high weight because most internal queries will match known patterns such as payment terms, platform components, and company policy lookups. | active | contextual | yes | |
| dca3260cbf4cdb95… | The retrieval pipeline should use a 3-strategy configuration tuned for internal knowledge patterns so that internal queries are handled according to expected query types. | active | contextual | yes | |
| d95974cd462e6943… | Ongoing ingestion must route daily research pipeline findings into PYRANA_PLATFORM as new research insights so that platform knowledge is continuously updated. | active | contextual | yes | |
| 68949bbb064fa795… | Ongoing ingestion must automatically classify and extract new documents added to Drive so that newly added files enter the knowledge graph without manual processing. | active | contextual | yes | |
| 1a756f6e38f3393a… | Ongoing ingestion must continuously map new Granola meeting notes into the CLIENTS and PROJECTS sets so that current meeting knowledge is captured as it is produced. | active | contextual | yes | |
| e5b7d1f515b545c1… | Phase 3 ingestion must classify remaining shared drive content into various sets so that uncategorized drive materials are distributed across appropriate knowledge domains. | active | contextual | yes | |
| 7e73b560f933c998… | Phase 3 ingestion must map patent documents into the IP_PATENTS set so that intellectual property records are stored in the designated patent category. | active | contextual | yes | |
| bb167647575ac431… | Phase 3 ingestion must map financial documents into the FINANCIAL_OPS set so that financial records are separated into the designated operational finance category. | active | contextual | yes | |
| 4f68ed1a61503de6… | Phase 3 ingestion must map security and compliance documents into the SECURITY_COMPLIANCE set so that governance-related records are classified consistently. | active | contextual | yes | |
| 01260538fa49becd… | Phase 3 ingestion must map remaining sales materials into the SALES_POSITIONING set so that sales-related content is organized under the correct knowledge category. | active | contextual | yes | |
| 372306d63bf857c0… | IP_PATENTS should be accessible only to Leadership and Engineering because intellectual property strategy is confidential. | active | contextual | yes | |
| e2961be9adc3ebf6… | FINANCIAL_OPS should be accessible only to Leadership because financial data is sensitive. | active | contextual | yes | |
| f1ed5f18057fc02b… | Executed CONTRACT_STANDARDS documents should be accessible only to Leadership and Legal because executed contracts may contain negotiated terms. | active | contextual | yes | |
| e145c32d5cb2e9b8… | CONTRACT_STANDARDS templates should be accessible to all team members because templates are reusable. | active | contextual | yes | |
| 2b7a50fc49f047db… | The PYRANA_PLATFORM set category should be accessible to all team members because platform knowledge is shared across the organization. | active | contextual | yes | |
| 40b5c4bc07ec1220… | The deployment is defined as single-tenant for Zeroth Agents internal use only, while still requiring the knowledge graph to enforce access scoping. | active | contextual | yes | |
| fcf5dca243f02075… | The AmbientAgent should enable gap detection to identify missing knowledge areas, including absent client security assessments and missing pricing models for the Code Interpreter tier. | active | contextual | yes | |
| 86666a542ef779b3… | The LearningAgent should enable TEMPR memory to learn which CXUs are most frequently retrieved together, such as MSA terms with SLA commitments, so that proposal generation can benefit from co-retrieval patterns. | active | contextual | yes | |
| 83d72d29104f9698… | Market estimates and projections should initialize CONTEXT_FOR edges with a Q-value of 0.45 because this source type is inherently uncertain. | active | contextual | yes | |
| b13148caed8c16f5… | GitHub CLAUDE.md files should initialize CONTEXT_FOR edges with a Q-value of 0.95 because they are authoritative, maintained documents. | active | contextual | yes | |
| 18a40902fb6d9945… | Initial Q-values for CONTEXT_FOR edges must be set according to source reliability so that retrieval confidence reflects the trustworthiness of each source type. | active | contextual | yes | |
| c47686113892e1a2… | Strategy 3, Text2Cypher, should start with lower weight and increase as the graph matures because it is intended to handle open-ended queries such as lessons learned and historical positioning changes. | active | contextual | yes | |
| 025c31811ebe3072… | Strategy 2, Edge-filter Cypher, should receive medium weight because it is useful for relationship-heavy queries involving graph edges such as client-project scoping and platform implementation references. | active | contextual | yes | |
| 329e34330127d975… | Strategy 1, Template Cypher, should receive high weight because most internal queries are expected to match known patterns such as contract requirements, relationship traversals, and policy lookups. | active | contextual | yes | |
| 9e8c10be4660401a… | The 3-strategy retrieval pipeline should be configured specifically for internal knowledge patterns so that retrieval behavior aligns with the organization’s common query types. | active | contextual | yes | |
| 4c860e00e577237d… | Daily research pipeline findings must be ingested into the PYRANA_PLATFORM set as new research insights so that platform knowledge incorporates ongoing research outputs. | active | contextual | yes | |
| 9133d70790ae5f91… | The ingestion system must automatically classify and extract new documents added to the shared Drive so that newly introduced content enters the knowledge graph without manual processing. | active | contextual | yes | |