Migrate all repos into monorepo context folders

Bahn: aisupport, Analyse-O2C-C2S, awesome-bahn-mcp-servers, beam-mcp, Confluence_Bot, db-planet-mcp-server, O2C-Harness, project-audit, Projekt-KIQ-HP, teamlandkarte-mcp Dhive: Jury-Voting Privat: CV, NoteGraph (NOTE: NoteGraph needs complete redo after consolidation) Shared: AI-Orchestrator, OrgMyLife, power_skills_and_more Shared/references: symphony (read-only) Bahn repos remain available as independent remotes - this monorepo pulls them in via subtree, the originals are untouched.
2026-06-30 20:39:52 +02:00
parent 2f2b295531
commit a5f8fb49ab
1717 changed files with 447332 additions and 0 deletions
@@ -0,0 +1,402 @@
+SPEC.md
+1. Executive Summary
+Product / Initiative Name
+
+Note-Graph
+
+Interviewed Stakeholder Role
+
+Owner, sponsor, project lead, and implementation orchestrator (“AI conductor”)
+
+Product Type
+
+New product
+
+Goal in One Sentence
+
+Create a personal knowledge infrastructure that enables reliable access to all notes, thoughts, decisions, and contextual information at any time in order to improve memory, prioritization, and project continuity.
+
+Short Business Context
+
+The stakeholder operates across many parallel projects, domains, meetings, and customer contexts. Information currently exists across handwritten notes, PDFs, meeting artifacts, task systems, Confluence spaces, and AI-generated summaries. The current process relies heavily on memory and chronological note-taking, causing information loss, weak follow-up tracking, and fragmented context retrieval.
+
+Primary Target Users
+Primary: Single knowledge worker / project orchestrator
+Future potential: Extended collaborative usage (currently out of scope)
+Core Functional Scope Summary
+
+The system shall:
+
+consolidate notes and knowledge artifacts from multiple formats and sources,
+support flexible tagging and contextual relationships,
+preserve historical context and traceability,
+enable fast contextual retrieval,
+connect notes with tasks, people, projects, and decisions,
+support gradual AI-assisted enrichment,
+maintain portability and data ownership.
+In Scope
+Personal knowledge management
+Cross-project contextual search
+Flexible labels/tags
+Relationships between notes, projects, people, tasks, and decisions
+Integration of handwritten notes and document-based sources
+Offline-capable note capture
+Mobile access
+Traceability between tasks and source context
+Export and publication workflows
+AI-assisted enrichment and retrieval
+Out of Scope
+Full project management platform
+CRM functionality
+Team collaboration platform
+Chat/messaging system
+Calendar replacement
+Complex automation workflows
+Autonomous AI agents
+Advanced graph visualization in first phase
+Semantic contradiction detection in first phase
+Main Open Questions
+Degree of automation vs manual curation
+How granular note segmentation should become in practice
+How historical relationship changes should be surfaced to users
+Scope of AI-generated suggestions in early versions
+Exact publication/export workflows
+Main Acceptance Indicators
+Relevant information can be retrieved during meetings.
+Meeting preparation becomes significantly easier.
+Contextual information can be found reliably across projects and time.
+Tasks remain traceable to their originating notes and decisions.
+2. Goal
+One-Sentence Goal
+
+Provide a durable, searchable, context-aware personal knowledge system that acts as an external memory and decision-support environment.
+
+Detailed Goal
+
+The system shall centralize fragmented knowledge sources and allow the stakeholder to:
+
+capture ideas quickly,
+retain project continuity,
+retrieve relevant context rapidly,
+preserve historical relationships,
+connect operational tasks with their originating discussions and decisions,
+maintain structure despite frequent context switching.
+Business Value
+Reduced information loss
+Better prioritization
+Faster meeting preparation
+Improved continuity across projects
+Reduced cognitive load
+Better follow-through on decisions and tasks
+Long-term retention of institutional and personal knowledge
+Intended Outcome for Users and Organization
+
+Users should be able to trust the system as a reliable external memory and operational context assistant.
+
+3. Stakeholder Context
+Respondent Role
+Owner
+Sponsor
+Project lead
+Implementation orchestrator (“AI conductor”)
+Perspective Represented
+
+Single stakeholder representing both business and implementation direction.
+
+Relevant Organizational or Customer Context
+
+The stakeholder works across multiple projects, domains, customers, and meeting contexts with heterogeneous documentation ecosystems.
+
+Whether This Spec Reflects One Interview Only
+
+Yes. This specification reflects a single interview.
+
+4. Target Users
+User Groups
+Primary User
+
+Knowledge worker managing many parallel projects and information streams.
+
+Potential Future Users
+
+Additional collaborators or project participants (currently out of scope).
+
+User Context
+
+Users frequently:
+
+switch contexts,
+attend meetings,
+create handwritten and digital notes,
+consume large document collections,
+derive tasks from discussions,
+revisit historical decisions.
+User Needs
+
+Users need to:
+
+retrieve information quickly,
+preserve context,
+avoid forgetting commitments,
+connect ideas across projects,
+maintain operational continuity,
+understand historical decisions.
+Pain Points
+Media breaks between tools and formats
+Difficulty finding information later
+Fragmented storage locations
+Reliance on memory
+Missing conversion from notes to tasks
+Weak cross-project traceability
+Loss of contextual continuity
+Important Differences Between Groups
+
+No differentiated user groups are currently defined.
+
+5. Current Situation / Current Process
+Current Process
+
+Information currently exists across:
+
+handwritten meeting notes,
+PDFs,
+Confluence spaces,
+task management tools,
+AI-assisted document search tools,
+digital note collections.
+
+Meeting notes are often incrementally extended over time and searched manually using:
+
+project names,
+dates,
+people,
+remembered context.
+Existing Workarounds
+Manual search
+AI-assisted document retrieval
+Chronological note accumulation
+Personal memory and contextual recall
+Main Gaps, Bottlenecks, and Failure Points
+Media discontinuity
+Information fragmentation
+Weak traceability
+Missing task extraction
+Incomplete prioritization
+Context loss across projects
+Inability to reliably recover ideas generated in unrelated contexts
+What Should Remain Unchanged
+Existing working style should remain largely compatible.
+Notes may continue to originate from different tools and formats.
+6. Functional Scope
+Main Capabilities
+
+The system shall:
+
+ingest and organize knowledge artifacts,
+support contextual relationships,
+preserve historical information,
+enable retrieval across projects and time,
+support flexible tagging and labeling,
+connect operational tasks to source knowledge,
+support gradual AI-assisted enrichment.
+Key User Interactions
+
+Users shall be able to:
+
+capture notes quickly,
+associate notes with multiple projects,
+associate notes with people and topics,
+split notes into smaller contextual fragments,
+search by content, project, person, or time,
+review historical decisions,
+export or publish derived content,
+revisit unresolved items.
+Major Functional Areas
+Knowledge capture
+Knowledge organization
+Search and retrieval
+Relationship management
+Task traceability
+Historical context management
+AI-assisted enrichment
+Export/publication support
+Role-Based Differences in Usage
+
+No differentiated role behavior currently defined.
+
+Relevant Triggers, Inputs, Outputs, and Outcomes
+Inputs
+Handwritten notes
+PDFs
+Markdown files
+Office documents
+Meeting artifacts
+AI-generated summaries
+Outputs
+Search results
+Structured contextual views
+Exported content
+Task references
+Meeting preparation material
+Outcomes
+Faster information access
+Improved continuity
+Better prioritization
+Reduced forgotten tasks and decisions
+7. Business Rules
+Notes may belong to multiple projects simultaneously.
+Relationships between entities may evolve over time.
+Historical assignments and timestamps must remain preserved.
+Original notes and source information must not be lost.
+Tasks must remain traceable to originating notes or decisions.
+Structured relationships and free-form associations must coexist.
+Offline capture capability is required.
+Mobile access is required.
+Users must retain control over AI-generated enrichments or suggestions.
+Relationship interpretation may change over time without overwriting historical truth.
+8. Business Objects / Functional Data Objects
+Note
+
+Represents a captured thought, meeting artifact, observation, or written content.
+
+Thought Fragment
+
+Represents a smaller extracted or separable unit derived from a larger note.
+
+Project
+
+Represents a business or operational context grouping related knowledge.
+
+Person
+
+Represents individuals connected to notes, tasks, meetings, or decisions.
+
+Task
+
+Represents actionable follow-up work derived from notes or decisions.
+
+Decision
+
+Represents an explicitly recorded outcome or conclusion.
+
+Source Document
+
+Represents imported or referenced material such as PDFs, Office documents, or AI-generated summaries.
+
+Label / Tag
+
+Represents flexible classification and contextual grouping metadata.
+
+Relationship
+
+Represents contextual connections between business objects.
+
+Time Context
+
+Represents historical assignment and chronological relevance.
+
+9. In Scope
+Personal knowledge graph functionality
+Multi-project note association
+Flexible tagging and labeling
+Contextual relationships
+Historical traceability
+Search by text, project, person, and time
+Mobile access
+Offline usage
+Handwritten note integration
+AI-assisted retrieval and enrichment
+Export and publishing workflows
+Task traceability to source context
+Gradual enrichment through review/question workflows
+10. Out of Scope
+Enterprise collaboration platform
+Full project management suite
+CRM capabilities
+Messaging/chat platform
+Calendar replacement
+Autonomous AI workflows
+Complex process automation
+Advanced graph visualizations in first release
+Automatic contradiction analysis in first release
+Fully automated prioritization
+11. Requirements
+Knowledge Capture
+The system shall allow users to capture notes quickly.
+The system shall support offline note capture.
+The system shall support mobile access.
+The system shall support handwritten note integration.
+The system shall support importing external document sources.
+Knowledge Organization
+The system shall allow notes to belong to multiple projects simultaneously.
+The system shall support labels and tags.
+The system shall support both structured and free-form relationships.
+The system shall allow users to split notes into smaller contextual fragments.
+The system shall preserve relationships between fragmented content and original source notes.
+Search and Retrieval
+The system shall provide full-text search.
+The system shall support contextual retrieval across projects and relationships.
+The system shall support search by people.
+The system shall support search by project.
+The system shall support time-based navigation and retrieval.
+The system shall allow users to retrieve meeting-relevant information quickly.
+Task Traceability
+The system shall support linking tasks to source notes or decisions.
+The system shall preserve the origin context of tasks.
+The system shall support identifying missing task metadata such as priorities or deadlines.
+Historical Integrity
+The system shall preserve original notes and timestamps.
+The system shall preserve historical relationship assignments over time.
+The system shall allow contextual relationships to evolve without losing historical information.
+AI Assistance
+The system shall support AI-assisted search and summarization.
+The system shall support AI-assisted enrichment and categorization.
+The system shall support gradual future expansion of AI capabilities.
+The system shall support review or quiz-style interactions for knowledge enrichment.
+Portability and Ownership
+The system shall support export of information and derived content.
+The system shall minimize dependency on proprietary structures.
+The system shall preserve user data ownership.
+The system shall support long-term portability and migration.
+12. Open Questions / Items to Clarify
+Desired level of automatic relationship generation
+Exact workflow for exporting/publishing to external systems
+Preferred granularity for note fragmentation
+Scope of AI-generated task extraction
+Desired review cadence for enrichment workflows
+Long-term collaboration requirements
+Definition of archival versus active information
+Rules for conflict resolution between changing contextual assignments
+13. Risks and Ambiguities
+Excessive maintenance effort may reduce adoption.
+Weak search quality could undermine trust in the system.
+Too many manual steps may interrupt workflows.
+Incorrect AI-generated relationships may reduce confidence.
+Information overload may reduce usability.
+Overly rigid structures may conflict with real-world usage patterns.
+Insufficient offline support may limit operational usefulness.
+Lack of clear contextual boundaries may create organizational confusion.
+Future migration requirements may conflict with short-term optimizations.
+14. Acceptance Perspective
+
+The product will be considered successful if:
+
+users can reliably retrieve relevant information during meetings,
+meeting preparation becomes significantly easier,
+contextual information can be recovered across projects and time,
+tasks remain traceable to their origin,
+users trust the system as an external memory,
+the system reduces forgotten follow-ups and lost context,
+users can maintain organization despite frequent context switching,
+knowledge remains portable and under user control.
+15. Glossary
+Original Term	English Explanation	Notes / Context
+Notiz-Graph	Note graph / knowledge graph system	Working title of the product
+KI-Dirigent	AI orchestrator	Stakeholder role coordinating AI-supported workflows
+Confluence	Knowledge collaboration platform	Existing documentation source
+NotebookLM	AI-supported document knowledge tool	Existing AI-generated summary source
+Labels	Context labels	Used for structured assignment
+Tags	Flexible metadata tags	Used for contextual classification
+Todo-App	Task management application	External task system
+Medienbruch	Media discontinuity	Fragmentation between formats/tools
+Gedächtnisstütze	Memory aid	Contextual reminder mechanism