arscontexta 0.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/marketplace.json +11 -0
- package/.claude-plugin/plugin.json +22 -0
- package/README.md +683 -0
- package/agents/knowledge-guide.md +49 -0
- package/bin/cli.mjs +66 -0
- package/generators/agents-md.md +240 -0
- package/generators/claude-md.md +379 -0
- package/generators/features/atomic-notes.md +124 -0
- package/generators/features/ethical-guardrails.md +58 -0
- package/generators/features/graph-analysis.md +188 -0
- package/generators/features/helper-functions.md +92 -0
- package/generators/features/maintenance.md +164 -0
- package/generators/features/methodology-knowledge.md +70 -0
- package/generators/features/mocs.md +144 -0
- package/generators/features/multi-domain.md +61 -0
- package/generators/features/personality.md +71 -0
- package/generators/features/processing-pipeline.md +428 -0
- package/generators/features/schema.md +149 -0
- package/generators/features/self-evolution.md +229 -0
- package/generators/features/self-space.md +78 -0
- package/generators/features/semantic-search.md +99 -0
- package/generators/features/session-rhythm.md +85 -0
- package/generators/features/templates.md +85 -0
- package/generators/features/wiki-links.md +88 -0
- package/generators/soul-md.md +121 -0
- package/hooks/hooks.json +45 -0
- package/hooks/scripts/auto-commit.sh +44 -0
- package/hooks/scripts/session-capture.sh +35 -0
- package/hooks/scripts/session-orient.sh +86 -0
- package/hooks/scripts/write-validate.sh +42 -0
- package/methodology/AI shifts knowledge systems from externalizing memory to externalizing attention.md +59 -0
- package/methodology/BM25 retrieval fails on full-length descriptions because query term dilution reduces match scores.md +39 -0
- package/methodology/IBIS framework maps claim-based architecture to structured argumentation.md +58 -0
- package/methodology/LLM attention degrades as context fills.md +49 -0
- package/methodology/MOC construction forces synthesis that automated generation from metadata cannot replicate.md +49 -0
- package/methodology/MOC maintenance investment compounds because orientation savings multiply across every future session.md +41 -0
- package/methodology/MOCs are attention management devices not just organizational tools.md +51 -0
- package/methodology/PKM failure follows a predictable cycle.md +50 -0
- package/methodology/ThreadMode to DocumentMode transformation is the core value creation step.md +52 -0
- package/methodology/WIP limits force processing over accumulation.md +53 -0
- package/methodology/Zeigarnik effect validates capture-first philosophy because open loops drain attention.md +42 -0
- package/methodology/academic research uses structured extraction with cross-source synthesis.md +566 -0
- package/methodology/adapt the four-phase processing pipeline to domain-specific throughput needs.md +197 -0
- package/methodology/agent notes externalize navigation intuition that search cannot discover and traversal cannot reconstruct.md +48 -0
- package/methodology/agent self-memory should be architecturally separate from user knowledge systems.md +48 -0
- package/methodology/agent session boundaries create natural automation checkpoints that human-operated systems lack.md +56 -0
- package/methodology/agent-cognition.md +107 -0
- package/methodology/agents are simultaneously methodology executors and subjects creating a unique trust asymmetry.md +66 -0
- package/methodology/aspect-oriented programming solved the same cross-cutting concern problem that hooks solve.md +39 -0
- package/methodology/associative ontologies beat hierarchical taxonomies because heterarchy adapts while hierarchy brittles.md +53 -0
- package/methodology/attention residue may have a minimum granularity that cannot be subdivided.md +46 -0
- package/methodology/auto-commit hooks eliminate prospective memory failures by converting remember-to-act into guaranteed execution.md +47 -0
- package/methodology/automated detection is always safe because it only reads state while automated remediation risks content corruption.md +42 -0
- package/methodology/automation should be retired when its false positive rate exceeds its true positive rate or it catches zero issues.md +56 -0
- package/methodology/backlinks implicitly define notes by revealing usage context.md +35 -0
- package/methodology/backward maintenance asks what would be different if written today.md +62 -0
- package/methodology/balance onboarding enforcement and questions to prevent premature complexity.md +229 -0
- package/methodology/basic level categorization determines optimal MOC granularity.md +51 -0
- package/methodology/batching by context similarity reduces switching costs in agent processing.md +43 -0
- package/methodology/behavioral anti-patterns matter more than tool selection.md +42 -0
- package/methodology/betweenness centrality identifies bridge notes connecting disparate knowledge domains.md +57 -0
- package/methodology/blueprints that teach construction outperform downloads that provide pre-built code for platform-dependent modules.md +42 -0
- package/methodology/bootstrapping principle enables self-improving systems.md +62 -0
- package/methodology/build automatic memory through cognitive offloading and session handoffs.md +285 -0
- package/methodology/capture the reaction to content not just the content itself.md +41 -0
- package/methodology/claims must be specific enough to be wrong.md +36 -0
- package/methodology/closure rituals create clean breaks that prevent attention residue bleed.md +44 -0
- package/methodology/cognitive offloading is the architectural foundation for vault design.md +46 -0
- package/methodology/cognitive outsourcing risk in agent-operated systems.md +55 -0
- package/methodology/coherence maintains consistency despite inconsistent inputs.md +96 -0
- package/methodology/coherent architecture emerges from wiki links spreading activation and small-world topology.md +48 -0
- package/methodology/community detection algorithms can inform when MOCs should split or merge.md +52 -0
- package/methodology/complete navigation requires four complementary types that no single mechanism provides.md +43 -0
- package/methodology/complex systems evolve from simple working systems.md +59 -0
- package/methodology/composable knowledge architecture builds systems from independent toggleable modules not monolithic templates.md +61 -0
- package/methodology/compose multi-domain systems through separate templates and shared graph.md +372 -0
- package/methodology/concept-orientation beats source-orientation for cross-domain connections.md +51 -0
- package/methodology/confidence thresholds gate automated action between the mechanical and judgment zones.md +50 -0
- package/methodology/configuration dimensions interact so choices in one create pressure on others.md +58 -0
- package/methodology/configuration paralysis emerges when derivation surfaces too many decisions.md +44 -0
- package/methodology/context files function as agent operating systems through self-referential self-extension.md +46 -0
- package/methodology/context phrase clarity determines how deep a navigation hierarchy can scale.md +46 -0
- package/methodology/continuous small-batch processing eliminates review dread.md +48 -0
- package/methodology/controlled disorder engineers serendipity through semantic rather than topical linking.md +51 -0
- package/methodology/creative writing uses worldbuilding consistency with character tracking.md +672 -0
- package/methodology/cross-links between MOC territories indicate creative leaps and integration depth.md +43 -0
- package/methodology/dangling links reveal which notes want to exist.md +62 -0
- package/methodology/data exit velocity measures how quickly content escapes vendor lock-in.md +74 -0
- package/methodology/decontextualization risk means atomicity may strip meaning that cannot be recovered.md +48 -0
- package/methodology/dense interlinked research claims enable derivation while sparse references only enable templating.md +47 -0
- package/methodology/dependency resolution through topological sort makes module composition transparent and verifiable.md +56 -0
- package/methodology/derivation generates knowledge systems from composable research claims not template customization.md +63 -0
- package/methodology/derivation-engine.md +27 -0
- package/methodology/derived systems follow a seed-evolve-reseed lifecycle.md +56 -0
- package/methodology/description quality for humans diverges from description quality for keyword search.md +73 -0
- package/methodology/descriptions are retrieval filters not summaries.md +112 -0
- package/methodology/design MOCs as attention management devices with lifecycle governance.md +318 -0
- package/methodology/design-dimensions.md +66 -0
- package/methodology/digital mutability enables note evolution that physical permanence forbids.md +54 -0
- package/methodology/discovery-retrieval.md +48 -0
- package/methodology/distinctiveness scoring treats description quality as measurable.md +69 -0
- package/methodology/does agent processing recover what fast capture loses.md +43 -0
- package/methodology/domain-compositions.md +37 -0
- package/methodology/dual-coding with visual elements could enhance agent traversal.md +55 -0
- package/methodology/each module must be describable in one sentence under 200 characters or it does too many things.md +45 -0
- package/methodology/each new note compounds value by creating traversal paths.md +55 -0
- package/methodology/eight configuration dimensions parameterize the space of possible knowledge systems.md +56 -0
- package/methodology/elaborative encoding is the quality gate for new notes.md +55 -0
- package/methodology/enforce schema with graduated strictness across capture processing and query zones.md +221 -0
- package/methodology/enforcing atomicity can create paralysis when ideas resist decomposition.md +43 -0
- package/methodology/engineering uses technical decision tracking with architectural memory.md +766 -0
- package/methodology/every knowledge domain shares a four-phase processing skeleton that diverges only in the process step.md +53 -0
- package/methodology/evolution observations provide actionable signals for system adaptation.md +67 -0
- package/methodology/external memory shapes cognition more than base model.md +60 -0
- package/methodology/faceted classification treats notes as multi-dimensional objects rather than folder contents.md +65 -0
- package/methodology/failure-modes.md +27 -0
- package/methodology/false universalism applies same processing logic regardless of domain.md +49 -0
- package/methodology/federated wiki pattern enables multi-agent divergence as feature not bug.md +59 -0
- package/methodology/flat files break at retrieval scale.md +75 -0
- package/methodology/forced engagement produces weak connections.md +48 -0
- package/methodology/four abstraction layers separate platform-agnostic from platform-dependent knowledge system features.md +47 -0
- package/methodology/fresh context per task preserves quality better than chaining phases.md +44 -0
- package/methodology/friction reveals architecture.md +63 -0
- package/methodology/friction-driven module adoption prevents configuration debt by adding complexity only at pain points.md +48 -0
- package/methodology/gardening cycle implements tend prune fertilize operations.md +41 -0
- package/methodology/generation effect gate blocks processing without transformation.md +40 -0
- package/methodology/goal-driven memory orchestration enables autonomous domain learning through directed compute allocation.md +41 -0
- package/methodology/good descriptions layer heuristic then mechanism then implication.md +57 -0
- package/methodology/graph-structure.md +65 -0
- package/methodology/guided notes might outperform post-hoc structuring for high-volume capture.md +37 -0
- package/methodology/health wellness uses symptom-trigger correlation with multi-dimensional tracking.md +819 -0
- package/methodology/hook composition creates emergent methodology from independent single-concern components.md +47 -0
- package/methodology/hook enforcement guarantees quality while instruction enforcement merely suggests it.md +51 -0
- package/methodology/hook-driven learning loops create self-improving methodology through observation accumulation.md +62 -0
- package/methodology/hooks are the agent habit system that replaces the missing basal ganglia.md +40 -0
- package/methodology/hooks cannot replace genuine cognitive engagement yet more automation is always tempting.md +87 -0
- package/methodology/hooks enable context window efficiency by delegating deterministic checks to external processes.md +47 -0
- package/methodology/idempotent maintenance operations are safe to automate because running them twice produces the same result as running them once.md +44 -0
- package/methodology/implement condition-based maintenance triggers for derived systems.md +255 -0
- package/methodology/implicit dependencies create distributed monoliths that fail silently across configurations.md +58 -0
- package/methodology/implicit knowledge emerges from traversal.md +55 -0
- package/methodology/incremental formalization happens through repeated touching of old notes.md +60 -0
- package/methodology/incremental reading enables cross-source connection finding.md +39 -0
- package/methodology/index.md +32 -0
- package/methodology/inline links carry richer relationship data than metadata fields.md +91 -0
- package/methodology/insight accretion differs from productivity in knowledge systems.md +41 -0
- package/methodology/intermediate packets enable assembly over creation.md +52 -0
- package/methodology/intermediate representation pattern enables reliable vault operations beyond regex.md +62 -0
- package/methodology/justification chains enable forward backward and evolution reasoning about configuration decisions.md +46 -0
- package/methodology/knowledge system architecture is parameterized by platform capabilities not fixed by methodology.md +51 -0
- package/methodology/knowledge systems become communication partners through complexity and memory humans cannot sustain.md +47 -0
- package/methodology/knowledge systems share universal operations and structural components across all methodology traditions.md +46 -0
- package/methodology/legal case management uses precedent chains with regulatory change propagation.md +892 -0
- package/methodology/live index via periodic regeneration keeps discovery current.md +58 -0
- package/methodology/local-first file formats are inherently agent-native.md +69 -0
- package/methodology/logic column pattern separates reasoning from procedure.md +35 -0
- package/methodology/maintenance operations are more universal than creative pipelines because structural health is domain-invariant.md +47 -0
- package/methodology/maintenance scheduling frequency should match consequence speed not detection capability.md +50 -0
- package/methodology/maintenance targeting should prioritize mechanism and theory notes.md +26 -0
- package/methodology/maintenance-patterns.md +72 -0
- package/methodology/markdown plus YAML plus ripgrep implements a queryable graph database without infrastructure.md +55 -0
- package/methodology/maturity field enables agent context prioritization.md +33 -0
- package/methodology/memory-architecture.md +27 -0
- package/methodology/metacognitive confidence can diverge from retrieval capability.md +42 -0
- package/methodology/metadata reduces entropy enabling precision over recall.md +91 -0
- package/methodology/methodology development should follow the trajectory from documentation to skill to hook as understanding hardens.md +80 -0
- package/methodology/methodology traditions are named points in a shared configuration space not competing paradigms.md +64 -0
- package/methodology/mnemonic medium embeds verification into navigation.md +46 -0
- package/methodology/module communication through shared YAML fields creates loose coupling without direct dependencies.md +44 -0
- package/methodology/module deactivation must account for structural artifacts that survive the toggle.md +49 -0
- package/methodology/multi-domain systems compose through separate templates and shared graph.md +61 -0
- package/methodology/multi-domain-composition.md +27 -0
- package/methodology/narrow folksonomy optimizes for single-operator retrieval unlike broad consensus tagging.md +53 -0
- package/methodology/navigation infrastructure passes through distinct scaling regimes that require qualitative strategy shifts.md +48 -0
- package/methodology/navigational vertigo emerges in pure association systems without local hierarchy.md +54 -0
- package/methodology/note titles should function as APIs enabling sentence transclusion.md +51 -0
- package/methodology/note-design.md +57 -0
- package/methodology/notes are skills /342/200/224 curated knowledge injected when relevant.md" +62 -0
- package/methodology/notes function as cognitive anchors that stabilize attention during complex tasks.md +41 -0
- package/methodology/novel domains derive by mapping knowledge type to closest reference domain then adapting.md +50 -0
- package/methodology/nudge theory explains graduated hook enforcement as choice architecture for agents.md +59 -0
- package/methodology/observation and tension logs function as dead-letter queues for failed automation.md +51 -0
- package/methodology/operational memory and knowledge memory serve different functions in agent architecture.md +48 -0
- package/methodology/operational wisdom requires contextual observation.md +52 -0
- package/methodology/orchestrated vault creation transforms arscontexta from tool to autonomous knowledge factory.md +40 -0
- package/methodology/organic emergence versus active curation creates a fundamental vault governance tension.md +68 -0
- package/methodology/orphan notes are seeds not failures.md +38 -0
- package/methodology/over-automation corrupts quality when hooks encode judgment rather than verification.md +62 -0
- package/methodology/people relationships uses Dunbar-layered graphs with interaction tracking.md +659 -0
- package/methodology/personal assistant uses life area management with review automation.md +610 -0
- package/methodology/platform adapter translation is semantic not mechanical because hook event meanings differ.md +40 -0
- package/methodology/platform capability tiers determine which knowledge system features can be implemented.md +48 -0
- package/methodology/platform fragmentation means identical conceptual operations require different implementations across agent environments.md +44 -0
- package/methodology/premature complexity is the most common derivation failure mode.md +45 -0
- package/methodology/prevent domain-specific failure modes through the vulnerability matrix.md +336 -0
- package/methodology/processing effort should follow retrieval demand.md +57 -0
- package/methodology/processing-workflows.md +75 -0
- package/methodology/product management uses feedback pipelines with experiment tracking.md +789 -0
- package/methodology/productivity porn risk in meta-system building.md +30 -0
- package/methodology/programmable notes could enable property-triggered workflows.md +64 -0
- package/methodology/progressive disclosure means reading right not reading less.md +69 -0
- package/methodology/progressive schema validates only what active modules require not the full system schema.md +49 -0
- package/methodology/project management uses decision tracking with stakeholder context.md +776 -0
- package/methodology/propositional link semantics transform wiki links from associative to reasoned.md +87 -0
- package/methodology/prospective memory requires externalization.md +53 -0
- package/methodology/provenance tracks where beliefs come from.md +62 -0
- package/methodology/queries evolve during search so agents should checkpoint.md +35 -0
- package/methodology/question-answer metadata enables inverted search patterns.md +39 -0
- package/methodology/random note resurfacing prevents write-only memory.md +33 -0
- package/methodology/reconciliation loops that compare desired state to actual state enable drift correction without continuous monitoring.md +59 -0
- package/methodology/reflection synthesizes existing notes into new insight.md +100 -0
- package/methodology/retrieval utility should drive design over capture completeness.md +69 -0
- package/methodology/retrieval verification loop tests description quality at scale.md +81 -0
- package/methodology/role field makes graph structure explicit.md +94 -0
- package/methodology/scaffolding enables divergence that fine-tuning cannot.md +67 -0
- package/methodology/schema enforcement via validation agents enables soft consistency.md +60 -0
- package/methodology/schema evolution follows observe-then-formalize not design-then-enforce.md +65 -0
- package/methodology/schema field names are the only domain specific element in the universal note pattern.md +46 -0
- package/methodology/schema fields should use domain-native vocabulary not abstract terminology.md +47 -0
- package/methodology/schema templates reduce cognitive overhead at capture time.md +55 -0
- package/methodology/schema validation hooks externalize inhibitory control that degrades under cognitive load.md +48 -0
- package/methodology/schema-enforcement.md +27 -0
- package/methodology/self-extension requires context files to contain platform operations knowledge not just methodology.md +47 -0
- package/methodology/sense-making vs storage does compression lose essential nuance.md +73 -0
- package/methodology/session boundary hooks implement cognitive bookends for orientation and reflection.md +60 -0
- package/methodology/session handoff creates continuity without persistent memory.md +43 -0
- package/methodology/session outputs are packets for future selves.md +43 -0
- package/methodology/session transcript mining enables experiential validation that structural tests cannot provide.md +38 -0
- package/methodology/skill context budgets constrain knowledge system complexity on agent platforms.md +52 -0
- package/methodology/skills encode methodology so manual execution bypasses quality gates.md +50 -0
- package/methodology/small-world topology requires hubs and dense local links.md +99 -0
- package/methodology/source attribution enables tracing claims to foundations.md +38 -0
- package/methodology/spaced repetition scheduling could optimize vault maintenance.md +44 -0
- package/methodology/spreading activation models how agents should traverse.md +79 -0
- package/methodology/stale navigation actively misleads because agents trust curated maps completely.md +43 -0
- package/methodology/stigmergy coordinates agents through environmental traces without direct communication.md +62 -0
- package/methodology/storage versus thinking distinction determines which tool patterns apply.md +56 -0
- package/methodology/structure enables navigation without reading everything.md +52 -0
- package/methodology/structure without processing provides no value.md +56 -0
- package/methodology/student learning uses prerequisite graphs with spaced retrieval.md +770 -0
- package/methodology/summary coherence tests composability before filing.md +37 -0
- package/methodology/tag rot applies to wiki links because titles serve as both identifier and display text.md +50 -0
- package/methodology/temporal media must convert to spatial text for agent traversal.md +43 -0
- package/methodology/temporal processing priority creates age-based inbox urgency.md +45 -0
- package/methodology/temporal separation of capture and processing preserves context freshness.md +39 -0
- package/methodology/ten universal primitives form the kernel of every viable agent knowledge system.md +162 -0
- package/methodology/testing effect could enable agent knowledge verification.md +38 -0
- package/methodology/the AgentSkills standard embodies progressive disclosure at the skill level.md +40 -0
- package/methodology/the derivation engine improves recursively as deployed systems generate observations.md +49 -0
- package/methodology/the determinism boundary separates hook methodology from skill methodology.md +46 -0
- package/methodology/the fix-versus-report decision depends on determinism reversibility and accumulated trust.md +45 -0
- package/methodology/the generation effect requires active transformation not just storage.md +57 -0
- package/methodology/the no wrong patches guarantee ensures any valid module combination produces a valid system.md +58 -0
- package/methodology/the system is the argument.md +46 -0
- package/methodology/the vault constitutes identity for agents.md +86 -0
- package/methodology/the vault methodology transfers because it encodes cognitive science not domain specifics.md +47 -0
- package/methodology/therapy journal uses warm personality with pattern detection for emotional processing.md +584 -0
- package/methodology/three capture schools converge through agent-mediated synthesis.md +55 -0
- package/methodology/three concurrent maintenance loops operate at different timescales to catch different classes of problems.md +56 -0
- package/methodology/throughput matters more than accumulation.md +58 -0
- package/methodology/title as claim enables traversal as reasoning.md +50 -0
- package/methodology/topological organization beats temporal for knowledge work.md +52 -0
- package/methodology/trading uses conviction tracking with thesis-outcome correlation.md +699 -0
- package/methodology/trails transform ephemeral navigation into persistent artifacts.md +39 -0
- package/methodology/transform universal vocabulary to domain-native language through six levels.md +259 -0
- package/methodology/type field enables structured queries without folder hierarchies.md +53 -0
- package/methodology/use-case presets dissolve the tension between composability and simplicity.md +44 -0
- package/methodology/vault conventions may impose hidden rigidity on thinking.md +44 -0
- package/methodology/verbatim risk applies to agents too.md +31 -0
- package/methodology/vibe notetaking is the emerging industry consensus for AI-native self-organization.md +56 -0
- package/methodology/vivid memories need verification.md +45 -0
- package/methodology/vocabulary-transformation.md +27 -0
- package/methodology/voice capture is the highest-bandwidth channel for agent-delegated knowledge systems.md +45 -0
- package/methodology/wiki links are the digital evolution of analog indexing.md +73 -0
- package/methodology/wiki links as social contract transforms agents into stewards of incomplete references.md +52 -0
- package/methodology/wiki links create navigation paths that shape retrieval.md +63 -0
- package/methodology/wiki links implement GraphRAG without the infrastructure.md +101 -0
- package/methodology/writing for audience blocks authentic creation.md +22 -0
- package/methodology/you operate a system that takes notes.md +79 -0
- package/openclaw/SKILL.md +110 -0
- package/package.json +45 -0
- package/platforms/README.md +51 -0
- package/platforms/claude-code/generator.md +61 -0
- package/platforms/claude-code/hooks/README.md +186 -0
- package/platforms/claude-code/hooks/auto-commit.sh.template +38 -0
- package/platforms/claude-code/hooks/session-capture.sh.template +72 -0
- package/platforms/claude-code/hooks/session-orient.sh.template +189 -0
- package/platforms/claude-code/hooks/write-validate.sh.template +106 -0
- package/platforms/openclaw/generator.md +82 -0
- package/platforms/openclaw/hooks/README.md +89 -0
- package/platforms/openclaw/hooks/bootstrap.ts.template +224 -0
- package/platforms/openclaw/hooks/command-new.ts.template +165 -0
- package/platforms/openclaw/hooks/heartbeat.ts.template +214 -0
- package/platforms/shared/features/README.md +70 -0
- package/platforms/shared/skill-blocks/graph.md +145 -0
- package/platforms/shared/skill-blocks/learn.md +119 -0
- package/platforms/shared/skill-blocks/next.md +131 -0
- package/platforms/shared/skill-blocks/pipeline.md +326 -0
- package/platforms/shared/skill-blocks/ralph.md +616 -0
- package/platforms/shared/skill-blocks/reduce.md +1142 -0
- package/platforms/shared/skill-blocks/refactor.md +129 -0
- package/platforms/shared/skill-blocks/reflect.md +780 -0
- package/platforms/shared/skill-blocks/remember.md +524 -0
- package/platforms/shared/skill-blocks/rethink.md +574 -0
- package/platforms/shared/skill-blocks/reweave.md +680 -0
- package/platforms/shared/skill-blocks/seed.md +320 -0
- package/platforms/shared/skill-blocks/stats.md +145 -0
- package/platforms/shared/skill-blocks/tasks.md +171 -0
- package/platforms/shared/skill-blocks/validate.md +323 -0
- package/platforms/shared/skill-blocks/verify.md +562 -0
- package/platforms/shared/templates/README.md +35 -0
- package/presets/experimental/categories.yaml +1 -0
- package/presets/experimental/preset.yaml +38 -0
- package/presets/experimental/starter/README.md +7 -0
- package/presets/experimental/vocabulary.yaml +7 -0
- package/presets/personal/categories.yaml +7 -0
- package/presets/personal/preset.yaml +41 -0
- package/presets/personal/starter/goals.md +21 -0
- package/presets/personal/starter/index.md +17 -0
- package/presets/personal/starter/life-areas.md +21 -0
- package/presets/personal/starter/people.md +21 -0
- package/presets/personal/vocabulary.yaml +32 -0
- package/presets/research/categories.yaml +8 -0
- package/presets/research/preset.yaml +41 -0
- package/presets/research/starter/index.md +17 -0
- package/presets/research/starter/methods.md +21 -0
- package/presets/research/starter/open-questions.md +21 -0
- package/presets/research/vocabulary.yaml +33 -0
- package/reference/AUDIT-REPORT.md +238 -0
- package/reference/claim-map.md +172 -0
- package/reference/components.md +327 -0
- package/reference/conversation-patterns.md +542 -0
- package/reference/derivation-validation.md +649 -0
- package/reference/dimension-claim-map.md +134 -0
- package/reference/evolution-lifecycle.md +297 -0
- package/reference/failure-modes.md +235 -0
- package/reference/interaction-constraints.md +204 -0
- package/reference/kernel.yaml +242 -0
- package/reference/methodology.md +283 -0
- package/reference/open-questions.md +279 -0
- package/reference/personality-layer.md +302 -0
- package/reference/self-space.md +299 -0
- package/reference/semantic-vs-keyword.md +288 -0
- package/reference/session-lifecycle.md +298 -0
- package/reference/templates/base-note.md +16 -0
- package/reference/templates/companion-note.md +70 -0
- package/reference/templates/creative-note.md +16 -0
- package/reference/templates/learning-note.md +16 -0
- package/reference/templates/life-note.md +16 -0
- package/reference/templates/moc.md +26 -0
- package/reference/templates/relationship-note.md +17 -0
- package/reference/templates/research-note.md +19 -0
- package/reference/templates/session-log.md +24 -0
- package/reference/templates/therapy-note.md +16 -0
- package/reference/test-fixtures/edge-case-constraints.md +148 -0
- package/reference/test-fixtures/multi-domain.md +164 -0
- package/reference/test-fixtures/novel-domain-gaming.md +138 -0
- package/reference/test-fixtures/research-minimal.md +102 -0
- package/reference/test-fixtures/therapy-full.md +155 -0
- package/reference/testing-milestones.md +1087 -0
- package/reference/three-spaces.md +363 -0
- package/reference/tradition-presets.md +203 -0
- package/reference/use-case-presets.md +341 -0
- package/reference/validate-kernel.sh +432 -0
- package/reference/vocabulary-transforms.md +85 -0
- package/scripts/sync-thinking.sh +147 -0
- package/skill-sources/graph/SKILL.md +567 -0
- package/skill-sources/graph/skill.json +17 -0
- package/skill-sources/learn/SKILL.md +254 -0
- package/skill-sources/learn/skill.json +17 -0
- package/skill-sources/next/SKILL.md +407 -0
- package/skill-sources/next/skill.json +17 -0
- package/skill-sources/pipeline/SKILL.md +314 -0
- package/skill-sources/pipeline/skill.json +17 -0
- package/skill-sources/ralph/SKILL.md +604 -0
- package/skill-sources/ralph/skill.json +17 -0
- package/skill-sources/reduce/SKILL.md +1113 -0
- package/skill-sources/reduce/skill.json +17 -0
- package/skill-sources/refactor/SKILL.md +448 -0
- package/skill-sources/refactor/skill.json +17 -0
- package/skill-sources/reflect/SKILL.md +747 -0
- package/skill-sources/reflect/skill.json +17 -0
- package/skill-sources/remember/SKILL.md +534 -0
- package/skill-sources/remember/skill.json +17 -0
- package/skill-sources/rethink/SKILL.md +658 -0
- package/skill-sources/rethink/skill.json +17 -0
- package/skill-sources/reweave/SKILL.md +657 -0
- package/skill-sources/reweave/skill.json +17 -0
- package/skill-sources/seed/SKILL.md +303 -0
- package/skill-sources/seed/skill.json +17 -0
- package/skill-sources/stats/SKILL.md +371 -0
- package/skill-sources/stats/skill.json +17 -0
- package/skill-sources/tasks/SKILL.md +402 -0
- package/skill-sources/tasks/skill.json +17 -0
- package/skill-sources/validate/SKILL.md +310 -0
- package/skill-sources/validate/skill.json +17 -0
- package/skill-sources/verify/SKILL.md +532 -0
- package/skill-sources/verify/skill.json +17 -0
- package/skills/add-domain/SKILL.md +441 -0
- package/skills/add-domain/skill.json +17 -0
- package/skills/architect/SKILL.md +568 -0
- package/skills/architect/skill.json +17 -0
- package/skills/ask/SKILL.md +388 -0
- package/skills/ask/skill.json +17 -0
- package/skills/health/SKILL.md +760 -0
- package/skills/health/skill.json +17 -0
- package/skills/help/SKILL.md +348 -0
- package/skills/help/skill.json +17 -0
- package/skills/recommend/SKILL.md +553 -0
- package/skills/recommend/skill.json +17 -0
- package/skills/reseed/SKILL.md +385 -0
- package/skills/reseed/skill.json +17 -0
- package/skills/setup/SKILL.md +1688 -0
- package/skills/setup/skill.json +17 -0
- package/skills/tutorial/SKILL.md +496 -0
- package/skills/tutorial/skill.json +17 -0
- package/skills/upgrade/SKILL.md +395 -0
- package/skills/upgrade/skill.json +17 -0
package/methodology/people relationships uses Dunbar-layered graphs with interaction tracking.md
ADDED
|
@@ -0,0 +1,659 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: people-relationships knowledge system — inspirational composition showing derived architecture for personal CRM with Dunbar-layered relationship graphs
|
|
3
|
+
kind: example
|
|
4
|
+
domain: relationships
|
|
5
|
+
topics: ["[[domain-compositions]]"]
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# people relationships uses Dunbar-layered graphs with interaction tracking
|
|
9
|
+
|
|
10
|
+
A derived architecture for someone who wants to maintain genuine relationships at scale. Not a database of contacts — a living social graph that remembers what you forget, notices what you miss, and surfaces connections you would never make on your own.
|
|
11
|
+
|
|
12
|
+
The agent translation is stark here. Humans maintain relationships through emotional memory, gut feelings, and social intuition. They are terrible at systematic maintenance across more than about fifteen people. Agents have no emotional memory but have perfect recall, exhaustive cross-referencing, and tireless attention across hundreds of contacts. The system leverages what agents do well (track, correlate, remind) to support what humans do well (empathize, connect, care).
|
|
13
|
+
|
|
14
|
+
---
|
|
15
|
+
|
|
16
|
+
## Persona
|
|
17
|
+
|
|
18
|
+
**Maya Chen** is a 34-year-old product designer who moved cities three times in the past decade. She has deep friendships from college, strong professional relationships from three different companies, a growing network from conference speaking, and family spread across two countries. She genuinely cares about people but regularly discovers she hasn't talked to someone important in months. She forgets details — someone's partner's name, that they mentioned a job change, that she promised to send an article. She has tried contact apps but they all feel like CRMs, treating friends like sales leads. What she wants is a system that helps her be the friend she already wants to be, not one that gamifies relationship maintenance.
|
|
19
|
+
|
|
20
|
+
Maya's agent operates as a social memory — not managing her relationships but remembering the texture of them. After a dinner party, Maya voice-captures a quick debrief. The agent extracts who was there, what they talked about, what follow-ups were mentioned, and how the evening felt. Three weeks later, when Maya is about to meet one of those people again, the agent surfaces the context: what they discussed last time, what was going on in their life, what Maya promised to do.
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## Configuration
|
|
25
|
+
|
|
26
|
+
| Dimension | Position | Rationale |
|
|
27
|
+
|-----------|----------|-----------|
|
|
28
|
+
| **Granularity** | Compound — one note per person, separate interaction logs | People are naturally compound entities. Atomizing a person into separate notes for "career," "family," and "preferences" would fragment what needs to be unified. Interactions are atomic because each event is distinct and timestamped. |
|
|
29
|
+
| **Organization** | Flat with Dunbar tiers as metadata | Folders by tier (inner-circle/, close-friends/) would force premature classification and create friction when relationships shift. Flat files with a `tier` field allow reclassification without moving files, and tier-based queries (`rg '^tier: inner-circle'`) replace folder navigation. |
|
|
30
|
+
| **Linking** | Explicit with semantic discovery for introductions | Person-to-person links must be intentional — Maya knows why two people are connected. But shared interest detection via semantic search surfaces introduction opportunities Maya would never think to look for. |
|
|
31
|
+
| **Metadata** | Medium density — enough for queries, light enough for quick capture | Person notes need structured fields (tier, last_contact, context_met) for automated maintenance queries. Interaction logs need minimal structure (date, people, channel) since the body carries the value. |
|
|
32
|
+
| **Processing** | Light — capture-focused with agent-driven enrichment | Maya captures quickly after conversations. The agent enriches: extracting follow-ups, updating last_contact, flagging tier mismatches. Heavy reduce-reflect cycles would add friction to a domain where speed of capture preserves emotional context. |
|
|
33
|
+
| **Formalization** | Medium — templates for people and interactions, free-form for everything else | Person notes benefit from consistent schemas (agents can query fields). But forcing schema on every social observation would kill the natural voice that makes relationship notes valuable. |
|
|
34
|
+
| **Review** | Weekly neglect scan, monthly tier review | Relationships decay on a weekly timescale for inner circle, monthly for close friends. Review cadence must match decay rate. The agent flags neglect; Maya decides what to do about it. |
|
|
35
|
+
| **Scope** | Personal only — no team collaboration | This is Maya's private social memory. Sharing it would change the dynamic from genuine care tracking to performative relationship management. |
|
|
36
|
+
|
|
37
|
+
---
|
|
38
|
+
|
|
39
|
+
## Vault Structure
|
|
40
|
+
|
|
41
|
+
```
|
|
42
|
+
vault/
|
|
43
|
+
├── self/
|
|
44
|
+
│ ├── identity.md
|
|
45
|
+
│ ├── relationships.md # MOC: Dunbar overview, tier thresholds
|
|
46
|
+
│ └── memory/
|
|
47
|
+
│ └── [personal reflections]
|
|
48
|
+
├── notes/
|
|
49
|
+
│ ├── index.md # Hub: entry point
|
|
50
|
+
│ ├── inner-circle.md # MOC: tier 1 (5 people)
|
|
51
|
+
│ ├── close-friends.md # MOC: tier 2 (15 people)
|
|
52
|
+
│ ├── active-network.md # MOC: tier 3 (50 people)
|
|
53
|
+
│ ├── wider-circle.md # MOC: tier 4 (150 people)
|
|
54
|
+
│ ├── contexts.md # MOC: how/where people connect
|
|
55
|
+
│ ├── shared-interests.md # MOC: topic-based groupings
|
|
56
|
+
│ │
|
|
57
|
+
│ ├── [person-name].md # Person notes (flat, one per person)
|
|
58
|
+
│ ├── [person-name].md
|
|
59
|
+
│ └── ...
|
|
60
|
+
├── interactions/
|
|
61
|
+
│ ├── 2026-02-14-dinner-at-sarahs.md
|
|
62
|
+
│ ├── 2026-02-10-coffee-with-james.md
|
|
63
|
+
│ └── ...
|
|
64
|
+
├── ops/
|
|
65
|
+
│ ├── templates/
|
|
66
|
+
│ │ ├── person.md
|
|
67
|
+
│ │ ├── interaction.md
|
|
68
|
+
│ │ ├── introduction-opportunity.md
|
|
69
|
+
│ │ └── gift-idea.md
|
|
70
|
+
│ ├── logs/
|
|
71
|
+
│ │ ├── neglect-alerts.md # Agent-generated maintenance log
|
|
72
|
+
│ │ └── tier-reviews.md # Monthly tier reassessment log
|
|
73
|
+
│ └── derivation.md # How this system was derived
|
|
74
|
+
└── inbox/
|
|
75
|
+
└── [quick captures, voice dumps]
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
---
|
|
79
|
+
|
|
80
|
+
## Note Schemas
|
|
81
|
+
|
|
82
|
+
### Person Note
|
|
83
|
+
|
|
84
|
+
```yaml
|
|
85
|
+
---
|
|
86
|
+
description: [one sentence about who this person is to Maya]
|
|
87
|
+
tier: inner-circle | close-friends | active-network | wider-circle
|
|
88
|
+
relationship: friend | family | colleague | mentor | mentee | acquaintance
|
|
89
|
+
context_met: [where/how they met]
|
|
90
|
+
location: [where they live]
|
|
91
|
+
last_contact: YYYY-MM-DD
|
|
92
|
+
contact_preference: text | call | in-person | email
|
|
93
|
+
important_dates:
|
|
94
|
+
- label: birthday
|
|
95
|
+
date: MM-DD
|
|
96
|
+
- label: anniversary
|
|
97
|
+
date: MM-DD
|
|
98
|
+
topics: ["[[inner-circle]]"]
|
|
99
|
+
relevant_people: ["[[person]] -- relationship context"]
|
|
100
|
+
---
|
|
101
|
+
```
|
|
102
|
+
|
|
103
|
+
### Interaction Log
|
|
104
|
+
|
|
105
|
+
```yaml
|
|
106
|
+
---
|
|
107
|
+
description: [one sentence summary of what happened]
|
|
108
|
+
date: YYYY-MM-DD
|
|
109
|
+
people: ["[[person-name]]"]
|
|
110
|
+
channel: in-person | call | text | email | video | group
|
|
111
|
+
mood: warm | neutral | tense | celebratory | vulnerable
|
|
112
|
+
follow_ups:
|
|
113
|
+
- task: [what was promised]
|
|
114
|
+
status: open | done
|
|
115
|
+
due: YYYY-MM-DD
|
|
116
|
+
topics: ["[[person-name]]"]
|
|
117
|
+
---
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
### Introduction Opportunity
|
|
121
|
+
|
|
122
|
+
```yaml
|
|
123
|
+
---
|
|
124
|
+
description: [why these two people should meet]
|
|
125
|
+
person_a: "[[person-name]]"
|
|
126
|
+
person_b: "[[person-name]]"
|
|
127
|
+
shared_interest: [what connects them]
|
|
128
|
+
context: [how the introduction would work]
|
|
129
|
+
status: identified | introduced | connected | declined
|
|
130
|
+
topics: ["[[shared-interests]]"]
|
|
131
|
+
---
|
|
132
|
+
```
|
|
133
|
+
|
|
134
|
+
### Gift Idea
|
|
135
|
+
|
|
136
|
+
```yaml
|
|
137
|
+
---
|
|
138
|
+
description: [what the gift is and why it would work]
|
|
139
|
+
person: "[[person-name]]"
|
|
140
|
+
category: book | experience | object | food | gesture
|
|
141
|
+
source: [how Maya learned about this preference]
|
|
142
|
+
occasions: ["birthday", "holiday", "just-because"]
|
|
143
|
+
status: idea | purchased | given
|
|
144
|
+
topics: ["[[person-name]]"]
|
|
145
|
+
---
|
|
146
|
+
```
|
|
147
|
+
|
|
148
|
+
---
|
|
149
|
+
|
|
150
|
+
## Example Notes
|
|
151
|
+
|
|
152
|
+
### Person Note: Sarah Okonkwo
|
|
153
|
+
|
|
154
|
+
```markdown
|
|
155
|
+
---
|
|
156
|
+
description: Maya's closest friend from college — lives in Portland, works in UX research, going through a career transition
|
|
157
|
+
tier: inner-circle
|
|
158
|
+
relationship: friend
|
|
159
|
+
context_met: Freshman year roommate at UMich, 2010
|
|
160
|
+
location: Portland, OR
|
|
161
|
+
last_contact: 2026-02-14
|
|
162
|
+
contact_preference: call
|
|
163
|
+
important_dates:
|
|
164
|
+
- label: birthday
|
|
165
|
+
date: 03-22
|
|
166
|
+
- label: daughter-mia-birthday
|
|
167
|
+
date: 09-15
|
|
168
|
+
topics: ["[[inner-circle]]"]
|
|
169
|
+
relevant_people: ["[[tom-okonkwo]] -- Sarah's husband, software engineer at Stripe", "[[james-holloway]] -- mutual friend from college, introduced through Maya"]
|
|
170
|
+
---
|
|
171
|
+
|
|
172
|
+
# Sarah Okonkwo
|
|
173
|
+
|
|
174
|
+
Sarah has been Maya's anchor across three city moves. They talk at least every two weeks, usually long phone calls while one of them is cooking dinner. Sarah is deeply thoughtful about her work and tends to undervalue her own expertise.
|
|
175
|
+
|
|
176
|
+
## Current context
|
|
177
|
+
|
|
178
|
+
Sarah is considering leaving her UX research lead role at Nike to start an independent consultancy. She has been thinking about this since November 2025 but hasn't told many people. The main hesitation is health insurance for Mia, who has asthma and needs regular specialist visits. Tom is supportive but cautious — his Stripe equity isn't fully vested until 2027.
|
|
179
|
+
|
|
180
|
+
Maya has offered to connect Sarah with [[priya-sharma]], who went independent three years ago and navigated the insurance question successfully.
|
|
181
|
+
|
|
182
|
+
## What matters to her
|
|
183
|
+
|
|
184
|
+
Sarah values depth over breadth in all things. She would rather have one real conversation than ten catch-ups. She is private about struggles and will only share vulnerabilities after being asked twice — the first ask gets "I'm fine," the second gets the truth. She loves handwritten letters, Japanese ceramics, and extremely specific coffee (currently obsessed with a Kenyan washed process from Heart Roasters).
|
|
185
|
+
|
|
186
|
+
## Sensitivities
|
|
187
|
+
|
|
188
|
+
Her mother passed away in 2024. The anniversary is in late June. She doesn't want big gestures around it, but appreciates a quiet check-in.
|
|
189
|
+
|
|
190
|
+
---
|
|
191
|
+
|
|
192
|
+
Relevant People:
|
|
193
|
+
- [[tom-okonkwo]] -- husband, met at a Portland design meetup in 2016
|
|
194
|
+
- [[james-holloway]] -- shared college friend, they reconnected through Maya in 2022
|
|
195
|
+
|
|
196
|
+
Topics:
|
|
197
|
+
- [[inner-circle]]
|
|
198
|
+
```
|
|
199
|
+
|
|
200
|
+
### Interaction Log: Dinner at Sarah's
|
|
201
|
+
|
|
202
|
+
```markdown
|
|
203
|
+
---
|
|
204
|
+
description: Dinner party at Sarah and Tom's — first time meeting their new neighbors, good conversation about Portland food scene and Sarah's consultancy plans
|
|
205
|
+
date: 2026-02-14
|
|
206
|
+
people: ["[[sarah-okonkwo]]", "[[tom-okonkwo]]"]
|
|
207
|
+
channel: in-person
|
|
208
|
+
mood: warm
|
|
209
|
+
follow_ups:
|
|
210
|
+
- task: Send Sarah the link to that independent consulting insurance broker Priya mentioned
|
|
211
|
+
status: open
|
|
212
|
+
due: 2026-02-17
|
|
213
|
+
- task: Text Tom the name of the natural wine shop in SE Portland
|
|
214
|
+
status: open
|
|
215
|
+
due: 2026-02-16
|
|
216
|
+
topics: ["[[sarah-okonkwo]]", "[[tom-okonkwo]]"]
|
|
217
|
+
---
|
|
218
|
+
|
|
219
|
+
# Dinner at Sarah's — Feb 14, 2026
|
|
220
|
+
|
|
221
|
+
Drove up to Portland for Valentine's weekend. Sarah and Tom hosted a small dinner — just us and their neighbors, David and Keiko. Mia was asleep by the time we arrived.
|
|
222
|
+
|
|
223
|
+
Sarah seemed lighter than the last few calls. She told the table about her consultancy plans, which is a big step — she had been keeping it close. Tom made his pasta alla norma, which was genuinely excellent. He's been watching a lot of Italian cooking YouTube and it's paying off.
|
|
224
|
+
|
|
225
|
+
The consultancy conversation got specific. Sarah has three potential anchor clients already but hasn't approached any of them formally. She is worried about the "asking" part — she can sell a research program inside a company but feels weird selling herself. I suggested she think of the initial conversations as research interviews, not sales pitches, since that reframes the dynamic into something she is already expert at. She seemed to genuinely light up at that reframing.
|
|
226
|
+
|
|
227
|
+
David and Keiko were easy company. David teaches environmental science at PSU. Keiko runs a ceramics studio — I should introduce her to [[elena-vasquez]] who has been looking for a ceramicist to collaborate with on that installation project.
|
|
228
|
+
|
|
229
|
+
Tom pulled me aside before dessert to ask if I thought Sarah was really ready to go independent. He wasn't being negative — he just wanted to know if her friends saw what he sees, which is that she is more capable than she believes. I told him yes, and that [[priya-sharma]] had the same wobble before going independent and is now turning away clients.
|
|
230
|
+
|
|
231
|
+
---
|
|
232
|
+
|
|
233
|
+
Relevant People:
|
|
234
|
+
- [[sarah-okonkwo]] -- consultancy plans becoming real, emotional shift toward readiness
|
|
235
|
+
- [[tom-okonkwo]] -- genuinely supportive, pasta game is strong
|
|
236
|
+
|
|
237
|
+
Topics:
|
|
238
|
+
- [[sarah-okonkwo]]
|
|
239
|
+
```
|
|
240
|
+
|
|
241
|
+
### Tier MOC: Inner Circle
|
|
242
|
+
|
|
243
|
+
```markdown
|
|
244
|
+
---
|
|
245
|
+
description: The five people Maya is closest to — requires weekly-to-biweekly contact, maximum relationship investment
|
|
246
|
+
type: moc
|
|
247
|
+
tier_threshold: contact every 2 weeks minimum
|
|
248
|
+
topics: ["[[index]]"]
|
|
249
|
+
---
|
|
250
|
+
|
|
251
|
+
# inner-circle
|
|
252
|
+
|
|
253
|
+
Dunbar's innermost layer: the five people Maya would call at 3am. These relationships require and deserve the most attention. The agent flags any inner-circle contact that goes beyond two weeks without interaction.
|
|
254
|
+
|
|
255
|
+
## Current Members
|
|
256
|
+
|
|
257
|
+
- [[sarah-okonkwo]] -- closest friend since college, currently navigating career transition to independent consultancy
|
|
258
|
+
- [[david-chen]] -- older brother, lives in Toronto, primary family anchor since parents moved to Taipei
|
|
259
|
+
- [[james-holloway]] -- college friend turned professional collaborator, co-presenting at Config 2026
|
|
260
|
+
- [[ana-lucia-reyes]] -- best friend from her Portland years, moved to Mexico City but they talk weekly
|
|
261
|
+
- [[mom-mei-lin]] -- Maya's mother, biweekly video calls, adjusting to Taipei life
|
|
262
|
+
|
|
263
|
+
## Maintenance cadence
|
|
264
|
+
|
|
265
|
+
Two weeks maximum between meaningful contact. "Meaningful" means a real conversation, not a react emoji on an Instagram story. The agent tracks `last_contact` on each person note and generates a neglect alert when any inner-circle member exceeds 14 days.
|
|
266
|
+
|
|
267
|
+
## Tier movement signals
|
|
268
|
+
|
|
269
|
+
Someone enters inner circle when: Maya instinctively wants to tell them news first; conversations regularly go over an hour; there is mutual vulnerability.
|
|
270
|
+
|
|
271
|
+
Someone leaves inner circle when: contact becomes obligatory rather than desired; conversations stay surface-level for three or more interactions; life circumstances create genuine distance (not just busyness).
|
|
272
|
+
|
|
273
|
+
---
|
|
274
|
+
|
|
275
|
+
Agent Notes:
|
|
276
|
+
- Inner circle is the only tier where neglect alerts should feel urgent. Close-friends alerts can wait for a weekly review; inner-circle alerts should surface immediately.
|
|
277
|
+
- When generating pre-meeting context for inner-circle members, include the last three interactions, not just the most recent. Pattern matters here.
|
|
278
|
+
|
|
279
|
+
Topics:
|
|
280
|
+
- [[index]]
|
|
281
|
+
```
|
|
282
|
+
|
|
283
|
+
### Introduction Opportunity Note
|
|
284
|
+
|
|
285
|
+
```markdown
|
|
286
|
+
---
|
|
287
|
+
description: Keiko (ceramicist, Sarah's neighbor) and Elena (looking for ceramics collaborator for gallery installation)
|
|
288
|
+
person_a: "[[keiko-tanaka]]"
|
|
289
|
+
person_b: "[[elena-vasquez]]"
|
|
290
|
+
shared_interest: ceramics — Keiko runs a studio, Elena needs a ceramicist for her gallery installation
|
|
291
|
+
context: Maya met Keiko at Sarah's dinner party, has known Elena through the Portland design community since 2023
|
|
292
|
+
status: identified
|
|
293
|
+
topics: ["[[shared-interests]]"]
|
|
294
|
+
---
|
|
295
|
+
|
|
296
|
+
# Keiko Tanaka and Elena Vasquez — ceramics collaboration
|
|
297
|
+
|
|
298
|
+
Noticed this connection at [[2026-02-14-dinner-at-sarahs]]. Keiko runs a ceramics studio in NE Portland and showed photos of her work on her phone — geometric forms with matte glazes that feel architectural. Elena has been talking since December about finding a ceramicist who thinks structurally rather than decoratively for her installation at the Newspace Center.
|
|
299
|
+
|
|
300
|
+
The styles are complementary, not identical. Keiko's work is precise and geometric; Elena's installations are organic and site-specific. That contrast could be genuinely interesting rather than just convenient.
|
|
301
|
+
|
|
302
|
+
## Before introducing
|
|
303
|
+
|
|
304
|
+
- Confirm with Elena that she is still looking (last mentioned it in January)
|
|
305
|
+
- Look at Keiko's portfolio online to make sure Maya's impression from phone photos holds up
|
|
306
|
+
- Think about framing: "someone whose work might complement yours" rather than "I found you a ceramicist"
|
|
307
|
+
|
|
308
|
+
---
|
|
309
|
+
|
|
310
|
+
Topics:
|
|
311
|
+
- [[shared-interests]]
|
|
312
|
+
```
|
|
313
|
+
|
|
314
|
+
### Person Note: Priya Sharma (Close Friends Tier)
|
|
315
|
+
|
|
316
|
+
```markdown
|
|
317
|
+
---
|
|
318
|
+
description: Maya's former manager at Nike turned independent UX research consultant — career mentor, practical advisor, navigated the freelance transition Maya's other friends are considering
|
|
319
|
+
tier: close-friends
|
|
320
|
+
relationship: mentor
|
|
321
|
+
context_met: Nike Design Team, 2019 — Priya was Maya's manager for two years
|
|
322
|
+
location: Seattle, WA
|
|
323
|
+
last_contact: 2026-01-28
|
|
324
|
+
contact_preference: video-call
|
|
325
|
+
important_dates:
|
|
326
|
+
- label: birthday
|
|
327
|
+
date: 08-11
|
|
328
|
+
topics: ["[[close-friends]]"]
|
|
329
|
+
relevant_people: ["[[sarah-okonkwo]] -- Maya wants to connect them re: independent consulting transition", "[[alex-kim]] -- also worked under Priya at Nike, still in touch"]
|
|
330
|
+
---
|
|
331
|
+
|
|
332
|
+
# Priya Sharma
|
|
333
|
+
|
|
334
|
+
Priya managed Maya during Maya's most formative professional years at Nike (2019-2021). She taught Maya to ground design decisions in research rather than intuition, a principle Maya still follows. Priya left Nike in 2022 to start an independent UX research consultancy and has been thriving — she now turns away clients.
|
|
335
|
+
|
|
336
|
+
## Current context
|
|
337
|
+
|
|
338
|
+
Priya's consultancy has grown to the point where she is considering whether to stay solo or bring on a junior researcher. She values autonomy but is hitting capacity limits on the projects she wants to take. Maya has suggested she talk to [[rafael-dominguez]], who went through the same decision with his design studio in Buenos Aires and ultimately hired a small team.
|
|
339
|
+
|
|
340
|
+
Priya is also a practical resource for [[sarah-okonkwo]]'s consulting transition — specifically on the health insurance question, which Priya navigated when she left Nike. Maya has been meaning to connect them but wants to do it thoughtfully, not transactionally.
|
|
341
|
+
|
|
342
|
+
## What matters to her
|
|
343
|
+
|
|
344
|
+
Priya is direct and efficient. She dislikes small talk and prefers conversations with an agenda, even social ones. She respects people who do their homework before asking for advice. She has a dry sense of humor that takes a few interactions to recognize.
|
|
345
|
+
|
|
346
|
+
She cares deeply about craft — she judges consultants by the quality of their research, not by their client list. She recommended Maya for the Config speaking opportunity because she saw Maya's work as rigorous, not because they are friends.
|
|
347
|
+
|
|
348
|
+
## Communication pattern
|
|
349
|
+
|
|
350
|
+
Video calls every 3-4 weeks, usually 45 minutes, usually with a topic. Priya does not do well with open-ended catch-ups — she prefers "I want to talk about X, what do you think?" Maya has learned to frame conversations that way and the relationship is stronger for it.
|
|
351
|
+
|
|
352
|
+
---
|
|
353
|
+
|
|
354
|
+
Relevant People:
|
|
355
|
+
- [[sarah-okonkwo]] -- potential connection for consulting insurance advice
|
|
356
|
+
- [[alex-kim]] -- shared Nike context
|
|
357
|
+
- [[rafael-dominguez]] -- potential connection for scaling a solo consultancy
|
|
358
|
+
|
|
359
|
+
Topics:
|
|
360
|
+
- [[close-friends]]
|
|
361
|
+
```
|
|
362
|
+
|
|
363
|
+
### Shared Interest Note
|
|
364
|
+
|
|
365
|
+
```markdown
|
|
366
|
+
---
|
|
367
|
+
description: The overlapping interest in independent consulting across Maya's network — Sarah considering it, Priya already doing it, James thinking about it
|
|
368
|
+
people: ["[[sarah-okonkwo]]", "[[priya-sharma]]", "[[james-holloway]]"]
|
|
369
|
+
topic: independent consulting transition
|
|
370
|
+
depth: active-conversation
|
|
371
|
+
topics: ["[[shared-interests]]"]
|
|
372
|
+
---
|
|
373
|
+
|
|
374
|
+
# Independent consulting interest cluster
|
|
375
|
+
|
|
376
|
+
Three people in Maya's network are at different stages of the same journey: leaving a full-time role to consult independently.
|
|
377
|
+
|
|
378
|
+
- [[sarah-okonkwo]] is in the consideration phase. Has potential anchor clients but hasn't made the leap. Main blocker is health insurance for her family.
|
|
379
|
+
- [[priya-sharma]] made the transition three years ago and is now thriving. She navigated the insurance question and could be a practical resource for Sarah.
|
|
380
|
+
- [[james-holloway]] has mentioned wanting to go independent "someday" but hasn't gotten concrete. He brings it up after frustrating weeks at work, then drops it when things improve.
|
|
381
|
+
|
|
382
|
+
There is a natural peer support group here, but Maya should be thoughtful about it. Sarah is private about her plans, and a group conversation would feel premature. The right move is probably a one-on-one between Sarah and Priya first, then bringing James in if Sarah is comfortable.
|
|
383
|
+
|
|
384
|
+
---
|
|
385
|
+
|
|
386
|
+
Topics:
|
|
387
|
+
- [[shared-interests]]
|
|
388
|
+
```
|
|
389
|
+
|
|
390
|
+
---
|
|
391
|
+
|
|
392
|
+
## Processing Workflow
|
|
393
|
+
|
|
394
|
+
### The Dunbar Model as Architecture
|
|
395
|
+
|
|
396
|
+
The Dunbar number layers are not just metadata — they are the architectural foundation that determines maintenance cadence, context depth, and agent behavior per contact.
|
|
397
|
+
|
|
398
|
+
| Layer | Size | Contact Cadence | Context Depth | Agent Behavior |
|
|
399
|
+
|-------|------|----------------|---------------|----------------|
|
|
400
|
+
| Inner circle | ~5 | Biweekly | Last 3 interactions, full context | Urgent neglect alerts, rich pre-meeting briefings |
|
|
401
|
+
| Close friends | ~15 | Monthly | Last 2 interactions, key context | Standard neglect alerts, moderate briefings |
|
|
402
|
+
| Active network | ~50 | Quarterly | Last interaction, headline context | Low-priority neglect alerts, light briefings |
|
|
403
|
+
| Wider circle | ~150 | Semi-annual | Name and relationship context only | Awareness-level tracking, no active alerting |
|
|
404
|
+
|
|
405
|
+
The agent calibrates its behavior to the tier. It does not alert Maya about a wider-circle contact she has not spoken to in four months — that is expected. It does alert her about an inner-circle member she has not spoken to in sixteen days — that is a problem.
|
|
406
|
+
|
|
407
|
+
Tier placement is not permanent. The agent tracks signals that suggest someone is operating at a different tier than their classification: frequency of interaction, depth of conversation (measured by interaction log length and mood tags), and reciprocity balance. When the signals diverge from the tier for three or more interactions, the agent suggests reclassification.
|
|
408
|
+
|
|
409
|
+
### Capture
|
|
410
|
+
|
|
411
|
+
Maya captures after conversations, usually by voice. She talks through what happened: who was there, what they discussed, what she noticed, what she promised to do. The agent receives the voice dump and extracts structured data.
|
|
412
|
+
|
|
413
|
+
**Capture triggers:**
|
|
414
|
+
- After any meaningful interaction (not transactional exchanges)
|
|
415
|
+
- When learning something new about someone (life event, preference, change)
|
|
416
|
+
- When noticing a potential introduction opportunity
|
|
417
|
+
- When a follow-up is promised
|
|
418
|
+
- When mood or energy of a relationship felt different than usual
|
|
419
|
+
|
|
420
|
+
### Process
|
|
421
|
+
|
|
422
|
+
The agent processes captures into structured notes:
|
|
423
|
+
|
|
424
|
+
1. **Create or update interaction log** — date, people, channel, mood, summary
|
|
425
|
+
2. **Extract follow-ups** — promised actions become tracked items with due dates
|
|
426
|
+
3. **Update person notes** — new information gets added to the relevant person's context section; `last_contact` updates automatically
|
|
427
|
+
4. **Detect introduction opportunities** — when two people share interests but do not know each other, the agent creates an introduction-opportunity note
|
|
428
|
+
5. **Flag tier mismatches** — if Maya is interacting with someone weekly but they are classified as `active-network`, the agent suggests reclassification
|
|
429
|
+
|
|
430
|
+
### Connect
|
|
431
|
+
|
|
432
|
+
The agent connects across the social graph:
|
|
433
|
+
|
|
434
|
+
- **Person-to-person links** — added via `relevant_people` when relationships are mentioned
|
|
435
|
+
- **Shared interest clustering** — when the same topic appears across multiple person notes, the agent creates or updates a shared-interest note
|
|
436
|
+
- **Interaction threading** — each interaction links back to person notes, creating a chronological trail per relationship
|
|
437
|
+
- **Gift/preference linking** — when someone mentions a preference in conversation, the agent creates a gift-idea note linked to that person
|
|
438
|
+
|
|
439
|
+
### Verify
|
|
440
|
+
|
|
441
|
+
Weekly maintenance cycle:
|
|
442
|
+
|
|
443
|
+
1. **Neglect scan** — check `last_contact` against tier thresholds (inner-circle: 14 days, close-friends: 30 days, active-network: 90 days, wider-circle: 180 days)
|
|
444
|
+
2. **Follow-up audit** — surface any open follow-ups past their due date
|
|
445
|
+
3. **Tier review** (monthly) — is anyone interacting at a different tier than their classification? Suggest reclassification
|
|
446
|
+
4. **Orphan check** — are any person notes disconnected from tier MOCs?
|
|
447
|
+
|
|
448
|
+
---
|
|
449
|
+
|
|
450
|
+
## MOC Structure
|
|
451
|
+
|
|
452
|
+
### Hub (index.md)
|
|
453
|
+
|
|
454
|
+
```markdown
|
|
455
|
+
---
|
|
456
|
+
description: Entry point for Maya's relationship knowledge system — navigate by tier, by context, or by shared interest
|
|
457
|
+
type: moc
|
|
458
|
+
---
|
|
459
|
+
|
|
460
|
+
# index
|
|
461
|
+
|
|
462
|
+
## By Tier (Dunbar layers)
|
|
463
|
+
- [[inner-circle]] -- 5 people, biweekly contact minimum
|
|
464
|
+
- [[close-friends]] -- 15 people, monthly contact minimum
|
|
465
|
+
- [[active-network]] -- 50 people, quarterly contact
|
|
466
|
+
- [[wider-circle]] -- 150 people, semi-annual awareness
|
|
467
|
+
|
|
468
|
+
## By Context
|
|
469
|
+
- [[contexts]] -- how and where people connect: college, work, conferences, neighborhood
|
|
470
|
+
|
|
471
|
+
## By Interest
|
|
472
|
+
- [[shared-interests]] -- topic-based groupings that cross tiers and contexts
|
|
473
|
+
|
|
474
|
+
## Maintenance
|
|
475
|
+
- [[neglect-alerts]] -- agent-generated flags for overdue contact
|
|
476
|
+
- [[tier-reviews]] -- monthly tier reassessment log
|
|
477
|
+
```
|
|
478
|
+
|
|
479
|
+
### Close Friends MOC (close-friends.md)
|
|
480
|
+
|
|
481
|
+
```markdown
|
|
482
|
+
---
|
|
483
|
+
description: The fifteen people Maya actively maintains meaningful relationships with — requires monthly contact, represents the sympathy group in Dunbar's model
|
|
484
|
+
type: moc
|
|
485
|
+
tier_threshold: contact every 30 days minimum
|
|
486
|
+
topics: ["[[index]]"]
|
|
487
|
+
---
|
|
488
|
+
|
|
489
|
+
# close-friends
|
|
490
|
+
|
|
491
|
+
Dunbar's second layer: the fifteen people Maya would invite to a small birthday dinner. These relationships are not as intensive as inner circle but are actively maintained, not passively held. The agent flags any close-friends contact that goes beyond 30 days without interaction.
|
|
492
|
+
|
|
493
|
+
## Current Members
|
|
494
|
+
- [[priya-sharma]] -- former manager at Nike, now independent consultant, practical career mentor
|
|
495
|
+
- [[elena-vasquez]] -- Portland design community, gallery installation artist, creative energy
|
|
496
|
+
- [[alex-kim]] -- design systems collaborator from Nike, still active professional relationship
|
|
497
|
+
- [[marcus-wright]] -- college study group, reconnected at Config 2024, works in accessibility
|
|
498
|
+
- [[rafael-dominguez]] -- Config 2025 co-panelist, runs design studio in Buenos Aires
|
|
499
|
+
- [[keiko-tanaka]] -- Sarah's neighbor, ceramicist, met at Feb 2026 dinner
|
|
500
|
+
- [[ben-nakamura]] -- David's college roommate, became Maya's friend independently, lives in SF
|
|
501
|
+
- [[lisa-worthington]] -- conference buddy, always at the same events, UX research lead at Figma
|
|
502
|
+
- [[tom-okonkwo]] -- Sarah's husband, but also genuinely Maya's friend in his own right
|
|
503
|
+
- [[diana-park]] -- former colleague from first job in Chicago, long-distance but consistent
|
|
504
|
+
- [[omar-hassan]] -- neighborhood friend from Portland years, still texts weekly
|
|
505
|
+
- [[jenny-liu]] -- cousin, lives in Vancouver, closest extended family relationship
|
|
506
|
+
- [[sam-reeves]] -- partner's sister, strong relationship independent of the partner
|
|
507
|
+
- [[carla-dubois]] -- met at a design retreat in 2023, deeply thoughtful, infrequent but rich conversations
|
|
508
|
+
- [[nate-sullivan]] -- friend from Portland climbing gym, outdoors-focused friendship
|
|
509
|
+
|
|
510
|
+
## Tier movement patterns
|
|
511
|
+
|
|
512
|
+
Close-friends is the most dynamic tier. People move in from active-network when relationships deepen, and occasionally move out to active-network when life creates distance. The agent tracks interaction frequency and depth: someone in close-friends who has had only transactional exchanges for three months may be drifting.
|
|
513
|
+
|
|
514
|
+
Recent movements:
|
|
515
|
+
- [[keiko-tanaka]] added February 2026 (previously wider-circle, upgraded after genuine connection at dinner)
|
|
516
|
+
- [[omar-hassan]] at risk of moving to active-network (last three interactions were brief texts, no substantive conversation since November)
|
|
517
|
+
|
|
518
|
+
---
|
|
519
|
+
|
|
520
|
+
Agent Notes:
|
|
521
|
+
- Close-friends is where relationship maintenance becomes non-trivial. Maya can intuitively maintain inner-circle. She needs agent support to maintain fifteen relationships at monthly cadence.
|
|
522
|
+
- Pre-meeting context for close-friends should include the last two interactions (not three, as with inner-circle). The interaction depth is lower, so less history is needed for context.
|
|
523
|
+
- When close-friends drift toward active-network interaction patterns, flag it gently: "Your last three interactions with Omar were brief texts. Would a longer conversation feel right?"
|
|
524
|
+
|
|
525
|
+
Topics:
|
|
526
|
+
- [[index]]
|
|
527
|
+
```
|
|
528
|
+
|
|
529
|
+
### Context MOC (contexts.md)
|
|
530
|
+
|
|
531
|
+
```markdown
|
|
532
|
+
---
|
|
533
|
+
description: Groups people by how Maya knows them — the social contexts that brought people into her life
|
|
534
|
+
type: moc
|
|
535
|
+
topics: ["[[index]]"]
|
|
536
|
+
---
|
|
537
|
+
|
|
538
|
+
# contexts
|
|
539
|
+
|
|
540
|
+
People enter Maya's life through contexts. These groupings matter because shared context predicts conversational comfort and suggests introduction opportunities within context clusters.
|
|
541
|
+
|
|
542
|
+
## College (UMich, 2010-2014)
|
|
543
|
+
- [[sarah-okonkwo]] -- freshman roommate, closest ongoing friendship
|
|
544
|
+
- [[james-holloway]] -- design program cohort, now professional collaborator
|
|
545
|
+
- [[marcus-wright]] -- study group, reconnected at a conference in 2024
|
|
546
|
+
|
|
547
|
+
## Nike Design Team (2019-2023)
|
|
548
|
+
- [[priya-sharma]] -- former manager, now independent consultant
|
|
549
|
+
- [[alex-kim]] -- design systems collaborator, still at Nike
|
|
550
|
+
|
|
551
|
+
## Conference Network
|
|
552
|
+
- [[elena-vasquez]] -- met at AIGA Portland 2023, gallery installation artist
|
|
553
|
+
- [[rafael-dominguez]] -- Config 2025 co-panelist, runs design studio in Buenos Aires
|
|
554
|
+
|
|
555
|
+
## Family
|
|
556
|
+
- [[david-chen]] -- older brother, Toronto
|
|
557
|
+
- [[mom-mei-lin]] -- mother, recently moved to Taipei
|
|
558
|
+
|
|
559
|
+
---
|
|
560
|
+
|
|
561
|
+
Agent Notes:
|
|
562
|
+
- Context clusters predict introduction success — people from the same context need no social lubrication. Cross-context introductions need more framing.
|
|
563
|
+
- When someone appears in multiple contexts (e.g., college friend who became a colleague), note the transition in their person file — it changes the relationship dynamic.
|
|
564
|
+
|
|
565
|
+
Topics:
|
|
566
|
+
- [[index]]
|
|
567
|
+
```
|
|
568
|
+
|
|
569
|
+
---
|
|
570
|
+
|
|
571
|
+
## Graph Query Examples
|
|
572
|
+
|
|
573
|
+
```bash
|
|
574
|
+
# Find all people Maya hasn't contacted in over 30 days
|
|
575
|
+
rg '^last_contact:' notes/*.md | while read line; do
|
|
576
|
+
file=$(echo "$line" | cut -d: -f1)
|
|
577
|
+
date=$(echo "$line" | awk '{print $2}')
|
|
578
|
+
if [[ "$date" < "2026-01-16" ]]; then
|
|
579
|
+
echo "$file — last contact: $date"
|
|
580
|
+
fi
|
|
581
|
+
done
|
|
582
|
+
|
|
583
|
+
# Find all open follow-ups across interactions
|
|
584
|
+
rg -U 'status: open' interactions/ -B 1
|
|
585
|
+
|
|
586
|
+
# Find all people in a specific tier
|
|
587
|
+
rg '^tier: close-friends' notes/
|
|
588
|
+
|
|
589
|
+
# Find all introduction opportunities still in "identified" status
|
|
590
|
+
rg '^status: identified' notes/ --glob '*introduction*'
|
|
591
|
+
|
|
592
|
+
# Find everyone who shares an interest in independent consulting
|
|
593
|
+
rg 'independent consult' notes/ -l
|
|
594
|
+
|
|
595
|
+
# Find all interactions with a specific person
|
|
596
|
+
rg '^\s*- "\[\[sarah-okonkwo\]\]"' interactions/ -l
|
|
597
|
+
|
|
598
|
+
# Surface gift ideas for upcoming birthdays
|
|
599
|
+
rg '^important_dates:' notes/ -A 3 | rg 'birthday' -A 1
|
|
600
|
+
```
|
|
601
|
+
|
|
602
|
+
---
|
|
603
|
+
|
|
604
|
+
## What Makes This Domain Unique
|
|
605
|
+
|
|
606
|
+
### The relationship graph is the primary artifact, not the individual notes
|
|
607
|
+
|
|
608
|
+
In a research vault, individual claim notes are the atomic units of value. In a relationship system, no person note is meaningful in isolation — the value lives in the connections between people, the interaction history that threads through them, and the patterns that emerge across the social graph. A person note without interaction logs, without connections to other people, without tier context, is just an address book entry. The graph makes it a social memory.
|
|
609
|
+
|
|
610
|
+
### Temporal decay is the dominant maintenance pressure
|
|
611
|
+
|
|
612
|
+
Research notes can sit untouched for months without losing value — a well-written claim about knowledge management is as true in June as in January. Relationships decay actively. Every day without contact moves a relationship closer to dormancy. This means maintenance is not periodic health-checking but continuous decay monitoring. The review dimension is not about note quality but about relationship health, and the cadence is measured in days and weeks, not months and quarters.
|
|
613
|
+
|
|
614
|
+
### Emotional texture is data the agent cannot generate but must preserve
|
|
615
|
+
|
|
616
|
+
The most valuable information in a relationship system is qualitative: how someone seemed, what the energy was like, what went unsaid. The agent cannot infer these from structured fields. Its job is to preserve the emotional texture Maya captures in voice dumps and interaction logs, and to surface it at the right moment — before the next interaction, when Maya needs to remember not just what happened but how it felt.
|
|
617
|
+
|
|
618
|
+
---
|
|
619
|
+
|
|
620
|
+
## Agent-Native Advantages
|
|
621
|
+
|
|
622
|
+
### Exhaustive neglect detection across Dunbar tiers
|
|
623
|
+
|
|
624
|
+
Maya can intuitively track whether she has talked to her five closest people recently. She cannot track fifty people with different contact cadences. The agent maintains a decay clock per person, calibrated to their tier threshold. Inner circle members get flagged at 14 days; active network members at 90 days. The flag is not "you should call this person" but "this relationship is approaching dormancy — is that intentional?" The agent distinguishes between intentional distance (Maya moved someone to a lower tier) and accidental neglect (life got busy and three months evaporated).
|
|
625
|
+
|
|
626
|
+
A human doing this manually would need to review a spreadsheet weekly and perform date arithmetic for 150+ contacts. The agent does it continuously, invisibly, and only surfaces what needs attention.
|
|
627
|
+
|
|
628
|
+
### Cross-graph introduction matching
|
|
629
|
+
|
|
630
|
+
Maya knows what her friends care about individually. She does not hold all 150 people's interests in working memory simultaneously. The agent does. When Maya captures that Keiko is a ceramicist, the agent can instantly cross-reference against every person note in the vault and surface Elena's months-old mention of needing a ceramics collaborator. This is not semantic search in the traditional sense — it is exhaustive pairwise comparison across the social graph, something a human literally cannot do across more than about fifteen contacts.
|
|
631
|
+
|
|
632
|
+
The introduction opportunities the agent surfaces are genuinely novel — connections Maya would never have thought to make because the relevant information lives in two different conversations months apart with people in different social contexts.
|
|
633
|
+
|
|
634
|
+
### Interaction pattern analysis that reveals relationship dynamics
|
|
635
|
+
|
|
636
|
+
Over six months of interaction logs, the agent can detect patterns invisible to Maya:
|
|
637
|
+
|
|
638
|
+
- **Reciprocity imbalance** — Maya always initiates with one friend; another friend always initiates with her. Neither pattern is inherently bad, but awareness changes behavior.
|
|
639
|
+
- **Mood trends** — interactions with a particular person have shifted from "warm" to "neutral" over three months. Something may have changed.
|
|
640
|
+
- **Topic evolution** — conversations with a colleague increasingly focus on frustration with their company, suggesting they may be considering a change.
|
|
641
|
+
- **Seasonal patterns** — Maya's social energy drops in February every year, leading to a cascade of neglect alerts. The agent can anticipate this and front-load outreach in January.
|
|
642
|
+
|
|
643
|
+
No human maintains a mental model of interaction patterns across 50+ relationships over months. The agent builds this model automatically from interaction logs Maya is already creating, transforming a byproduct of good capture into genuine social intelligence.
|
|
644
|
+
|
|
645
|
+
### Pre-meeting context synthesis
|
|
646
|
+
|
|
647
|
+
Before Maya meets someone, the agent assembles a contextual briefing: the last three interactions, any open follow-ups, recent life events mentioned in previous conversations, any relevant updates from mutual connections. This is not just "when did you last talk" — it is "here is the conversational landscape so you can be fully present instead of spending the first ten minutes catching up on logistics."
|
|
648
|
+
|
|
649
|
+
The human equivalent of this would be re-reading months of journal entries before every meeting. Nobody does that. The agent does it in seconds, every time, without being asked.
|
|
650
|
+
|
|
651
|
+
### Gift and gesture memory that never fades
|
|
652
|
+
|
|
653
|
+
When Sarah mentions in passing during a February dinner that she has been obsessed with Kenyan washed process coffee from Heart Roasters, Maya will forget this by March. The agent will not. When Sarah's birthday arrives in three weeks, the agent surfaces this alongside every other preference and gift idea accumulated over years of interactions. The result is not "I remembered" (which humans do unreliably) but "I always remember" (which only an agent can guarantee).
|
|
654
|
+
|
|
655
|
+
This extends beyond gifts to all social gestures: remembering to ask about someone's mother's surgery, following up on a job interview they mentioned six weeks ago, noting that they said they were reading a book Maya also loved. Each individual act of remembering is small. The cumulative effect of never forgetting is transformative — it communicates care through consistency that humans cannot sustain across a large network.
|
|
656
|
+
---
|
|
657
|
+
|
|
658
|
+
Topics:
|
|
659
|
+
- [[domain-compositions]]
|