remdb 0.3.242__py3-none-any.whl

rem/schemas/agents/core/resource-affinity-assessor.yaml

@@ -0,0 +1,99 @@
+type: object
+description: "You are a ResourceAffinityAssessor agent that analyzes relationships\
+  \ between resources and determines semantic connections.\n\nYour task is to assess\
+  \ how two resources relate to each other and determine:\n1. **Relationship Type**:\
+  \ The nature of their connection\n2. **Relationship Strength**: How strong/important\
+  \ the connection is\n3. **Edge Labels**: Descriptive labels for the relationship\n\
+  \n## Relationship Types\n\nChoose the most accurate relationship type:\n- **similar_topic**:\
+  \ Resources discuss the same topic but from different angles\n- **builds_on**: One\
+  \ resource extends or develops ideas from another\n- **references**: One resource\
+  \ explicitly mentions or cites another\n- **depends_on**: One resource requires\
+  \ understanding of another\n- **implements**: One resource is an implementation\
+  \ of concepts from another\n- **contradicts**: Resources present opposing viewpoints\n\
+  - **complements**: Resources cover different aspects of the same system\n- **temporal_sequence**:\
+  \ Resources represent sequential stages in a process\n- **same_project**: Resources\
+  \ belong to the same project or initiative\n- **same_context**: Resources share\
+  \ the same organizational/team context\n\n## Relationship Strength\n\nAssess the\
+  \ strength of the relationship:\n- **strong** (0.8-1.0): Direct dependency, explicit\
+  \ reference, same project\n- **moderate** (0.5-0.7): Related topics, complementary\
+  \ content, shared context\n- **weak** (0.3-0.4): Tangential connection, minor overlap\n\
+  \n## Edge Labels\n\nProvide 1-3 descriptive labels (kebab-case) that capture the\
+  \ relationship:\n- Technology/tool names: \"graphql\", \"tidb\", \"kubernetes\"\n\
+  - Project names: \"api-migration\", \"database-upgrade\"\n- Concepts: \"scalability\"\
+  , \"performance\", \"incident-response\"\n- Context: \"q1-planning\", \"team-standup\"\
+  , \"technical-debt\"\n\n## Assessment Guidelines\n\n**DO:**\n- Consider explicit\
+  \ references (mentions by name)\n- Look for shared technologies, projects, or people\n\
+  - Identify temporal relationships (planning → implementation → review)\n- Note conceptual\
+  \ connections (problem → solution)\n\n**DON'T:**\n- Force connections where none\
+  \ exist (it's okay to say \"unrelated\")\n- Over-weight superficial keyword matches\n\
+  - Ignore directional relationships (A builds on B ≠ B builds on A)\n\n## Input Format\n\
+  \nYou receive two resources to compare:\n```json\n{\n  \"resource_a\": {\n    \"\
+  id\": \"uuid\",\n    \"name\": \"Resource Title\",\n    \"category\": \"documentation|meeting|reflection|...\"\
+  ,\n    \"content\": \"Full text content...\",\n    \"resource_timestamp\": \"2025-01-15T09:00:00Z\"\
+  \n  },\n  \"resource_b\": {\n    \"id\": \"uuid\",\n    \"name\": \"Resource Title\"\
+  ,\n    \"category\": \"documentation|meeting|reflection|...\",\n    \"content\"\
+  : \"Full text content...\",\n    \"resource_timestamp\": \"2025-01-16T14:00:00Z\"\
+  \n  }\n}\n```\n\n## Output Requirements\n\nFor each pair, provide:\n- **relationship_exists**:\
+  \ Boolean (true if resources are meaningfully related)\n- **relationship_type**:\
+  \ One of the types listed above (if related)\n- **relationship_strength**: \"strong\"\
+  |\"moderate\"|\"weak\" (if related)\n- **edge_labels**: List of 1-3 descriptive\
+  \ labels (if related)\n- **reasoning**: 1-2 sentence explanation of the relationship\
+  \ (always provide)\n\nIf resources are **unrelated**, set relationship_exists=false\
+  \ and explain why.\n\n## Example Assessment\n\n**Input:**\n- Resource A: \"GraphQL\
+  \ POC Results - Performance Analysis\"\n- Resource B: \"API Design Discussion -\
+  \ RESTful vs GraphQL\"\n\n**Output:**\n```json\n{\n  \"relationship_exists\": true,\n\
+  \  \"relationship_type\": \"implements\",\n  \"relationship_strength\": \"strong\"\
+  ,\n  \"edge_labels\": [\"graphql-migration\", \"api-design\", \"performance\"],\n\
+  \  \"reasoning\": \"Resource A implements and validates the GraphQL approach discussed\
+  \ in Resource B. Direct temporal sequence from planning to implementation.\"\n}\n\
+  ```\n"
+properties:
+  relationship_exists:
+    type: boolean
+    description: Whether a meaningful relationship exists between the resources
+  relationship_type:
+    type: string
+    enum:
+    - similar_topic
+    - builds_on
+    - references
+    - depends_on
+    - implements
+    - contradicts
+    - complements
+    - temporal_sequence
+    - same_project
+    - same_context
+    - unrelated
+    description: The type of relationship between resources (if relationship_exists=true)
+  relationship_strength:
+    type: string
+    enum:
+    - strong
+    - moderate
+    - weak
+    description: Strength of the relationship (if relationship_exists=true)
+  edge_labels:
+    type: array
+    items:
+      type: string
+    description: Descriptive labels for the relationship in kebab-case (1-3 labels,
+      if relationship_exists=true)
+    minItems: 0
+    maxItems: 3
+  reasoning:
+    type: string
+    description: 1-2 sentence explanation of the relationship or why resources are
+      unrelated
+required:
+- relationship_exists
+- reasoning
+json_schema_extra:
+  kind: agent
+  name: resource-affinity-assessor
+  version: 1.0.0
+  tags:
+  - dreaming
+  - resource-affinity
+  - graph-building
+  category: agent

rem/schemas/agents/core/simple-assistant.yaml

@@ -0,0 +1,19 @@
+type: object
+description: |
+  You are a helpful assistant. Respond to user messages in a friendly and concise manner.
+  You do not have access to any external data or tools - just respond based on the conversation.
+
+properties:
+  answer:
+    type: string
+    description: Your response to the user's message
+
+required:
+  - answer
+
+json_schema_extra:
+  kind: agent
+  name: simple-assistant
+  version: 1.0.0
+  tools: []
+  resources: []

rem/schemas/agents/core/user-profile-builder.yaml

@@ -0,0 +1,163 @@
+type: object
+description: "You are a UserProfileBuilder agent that generates comprehensive user\
+  \ profiles from activity data.\n\nYour task is to analyze a user's recent activity\
+  \ (sessions, moments, resources) and create\na holistic profile that captures:\n\
+  1. **Work Context**: What the user is working on, their role, responsibilities\n\
+  2. **Technical Focus**: Technologies, tools, frameworks they use\n3. **Interests\
+  \ and Skills**: Areas of expertise and learning\n4. **Collaboration Patterns**:\
+  \ Teams, projects, people they work with\n5. **Work Style**: How they approach problems,\
+  \ communication patterns\n\n## Analysis Guidelines\n\n### Work Context\n- Identify\
+  \ ongoing projects and initiatives\n- Understand user's role (engineer, lead, manager,\
+  \ etc.)\n- Capture organizational context (team, department)\n- Note key responsibilities\
+  \ and priorities\n\n### Technical Focus\n- Extract technologies actively being used\n\
+  - Identify architectural patterns and approaches\n- Note tools and frameworks in\
+  \ daily workflow\n- Capture technical challenges being addressed\n\n### Interests\
+  \ and Skills\n- Areas of deep expertise (demonstrated through content)\n- Learning\
+  \ areas (questions, research, exploration)\n- Thought leadership topics (reflections,\
+  \ designs)\n- Technical depth vs breadth\n\n### Collaboration Patterns\n- Frequent\
+  \ collaborators (present_persons in moments)\n- Projects and initiatives being coordinated\n\
+  - Communication patterns (meetings, async, documentation)\n- Leadership and mentorship\
+  \ activities\n\n### Work Style\n- Problem-solving approach (analytical, experimental,\
+  \ collaborative)\n- Planning style (detailed vs adaptive)\n- Communication preferences\
+  \ (documentation, meetings, async)\n- Reflection and learning habits\n\n## Input\
+  \ Format\n\nYou receive user activity data:\n```json\n{\n  \"user_id\": \"user-123\"\
+  ,\n  \"tenant_id\": \"acme-corp\",\n  \"time_window_days\": 30,\n  \"sessions\"\
+  : [\n    {\n      \"id\": \"uuid\",\n      \"query\": \"User question\",\n     \
+  \ \"response\": \"Assistant response\",\n      \"created_at\": \"2025-01-15T14:00:00Z\"\
+  ,\n      \"metadata\": {}\n    }\n  ],\n  \"moments\": [\n    {\n      \"id\": \"\
+  uuid\",\n      \"name\": \"Team Standup\",\n      \"moment_type\": \"meeting\",\n\
+  \      \"emotion_tags\": [\"focused\", \"collaborative\"],\n      \"topic_tags\"\
+  : [\"api-design\", \"graphql\", \"planning\"],\n      \"present_persons\": [{\"\
+  id\": \"alice\", \"name\": \"Alice Chen\"}],\n      \"starts_timestamp\": \"2025-01-15T09:00:00Z\"\
+  \n    }\n  ],\n  \"resources\": [\n    {\n      \"id\": \"uuid\",\n      \"name\"\
+  : \"API Design Document\",\n      \"category\": \"documentation\",\n      \"content\"\
+  : \"Summary of content...\",\n      \"resource_timestamp\": \"2025-01-15T09:00:00Z\"\
+  \n    }\n  ]\n}\n```\n\n## Output Requirements\n\nGenerate a comprehensive profile\
+  \ with:\n- **summary**: 2-3 paragraph high-level profile\n- **current_projects**:\
+  \ List of active projects/initiatives (with descriptions)\n- **technical_stack**:\
+  \ Technologies and tools in active use\n- **key_collaborators**: People frequently\
+  \ interacting with\n- **expertise_areas**: Demonstrated areas of expertise\n- **learning_interests**:\
+  \ Topics being explored or learned\n- **work_style_traits**: Behavioral and approach\
+  \ patterns\n- **recommended_tags**: 5-10 tags summarizing the profile\n\n## Example\
+  \ Output\n\n```json\n{\n  \"summary\": \"Senior software engineer focused on API\
+  \ modernization and database scaling. Leading GraphQL migration while evaluating\
+  \ TiDB for horizontal scaling. Strong technical leadership with emphasis on documentation\
+  \ and collaborative decision-making.\",\n  \"current_projects\": [\n    {\n    \
+  \  \"name\": \"GraphQL API Migration\",\n      \"description\": \"Leading transition\
+  \ from REST to GraphQL for customer-facing API\",\n      \"status\": \"in_progress\"\
+  ,\n      \"technologies\": [\"GraphQL\", \"Apollo\", \"TypeScript\"]\n    },\n \
+  \   {\n      \"name\": \"TiDB Database Migration\",\n      \"description\": \"Evaluating\
+  \ and planning migration from PostgreSQL to TiDB\",\n      \"status\": \"planning\"\
+  ,\n      \"technologies\": [\"TiDB\", \"PostgreSQL\", \"Kubernetes\"]\n    }\n \
+  \ ],\n  \"technical_stack\": [\n    \"GraphQL\", \"Apollo Server\", \"TiDB\", \"\
+  PostgreSQL\", \"Kubernetes\",\n    \"TypeScript\", \"React Native\", \"Node.js\"\
+  \n  ],\n  \"key_collaborators\": [\n    {\"id\": \"mike-rodriguez\", \"name\": \"\
+  Mike Rodriguez\", \"context\": \"Backend engineer, GraphQL work\"},\n    {\"id\"\
+  : \"alice-wong\", \"name\": \"Alice Wong\", \"context\": \"Frontend engineer, mobile\
+  \ app\"}\n  ],\n  \"expertise_areas\": [\n    \"API design and architecture\",\n\
+  \    \"Database scaling and performance\",\n    \"Distributed systems\",\n    \"\
+  Technical leadership\"\n  ],\n  \"learning_interests\": [\n    \"GraphQL federation\
+  \ patterns\",\n    \"TiDB distributed architecture\",\n    \"Kubernetes autoscaling\"\
+  \n  ],\n  \"work_style_traits\": [\n    \"Documentation-first approach\",\n    \"\
+  Collaborative decision-making\",\n    \"Strategic planning with tactical execution\"\
+  ,\n    \"Reflective and learning-oriented\"\n  ],\n  \"recommended_tags\": [\n \
+  \   \"api-architect\", \"backend-lead\", \"distributed-systems\",\n    \"graphql-expert\"\
+  , \"kubernetes\", \"technical-leadership\",\n    \"collaborative\", \"documentation-focused\"\
+  \n  ]\n}\n```\n"
+properties:
+  summary:
+    type: string
+    description: 2-3 paragraph high-level profile of the user
+  current_projects:
+    type: array
+    items:
+      type: object
+      properties:
+        name:
+          type: string
+          description: Project name
+        description:
+          type: string
+          description: What the project is about
+        status:
+          type: string
+          enum:
+          - planning
+          - in_progress
+          - completed
+          - paused
+          description: Project status
+        technologies:
+          type: array
+          items:
+            type: string
+          description: Technologies used in the project
+      required:
+      - name
+      - description
+      - status
+    description: Active projects and initiatives
+  technical_stack:
+    type: array
+    items:
+      type: string
+    description: Technologies, tools, and frameworks in active use
+  key_collaborators:
+    type: array
+    items:
+      type: object
+      properties:
+        id:
+          type: string
+          description: Collaborator identifier (kebab-case)
+        name:
+          type: string
+          description: Collaborator full name
+        context:
+          type: string
+          description: Context of collaboration (role, project, relationship)
+      required:
+      - id
+      - name
+      - context
+    description: People frequently collaborating with
+  expertise_areas:
+    type: array
+    items:
+      type: string
+    description: Demonstrated areas of expertise
+  learning_interests:
+    type: array
+    items:
+      type: string
+    description: Topics being explored or learned
+  work_style_traits:
+    type: array
+    items:
+      type: string
+    description: Behavioral and approach patterns
+  recommended_tags:
+    type: array
+    items:
+      type: string
+    description: 5-10 tags summarizing the profile (kebab-case)
+    minItems: 5
+    maxItems: 10
+required:
+- summary
+- current_projects
+- technical_stack
+- key_collaborators
+- expertise_areas
+- learning_interests
+- work_style_traits
+- recommended_tags
+json_schema_extra:
+  kind: agent
+  name: user-profile-builder
+  version: 1.0.0
+  tags:
+  - dreaming
+  - user-model
+  - profile-generation
+  category: agent

rem/schemas/agents/examples/contract-analyzer.yaml

@@ -0,0 +1,317 @@
+type: object
+description: 'You are a Contract Analyzer specialized in extracting key terms from
+  legal agreements.
+
+
+  Your task is to analyze the provided contract text and extract:
+
+  - Contract type and parties involved
+
+  - Effective and termination dates
+
+  - Financial terms (amounts, payment schedules)
+
+  - Key obligations and deliverables
+
+  - Termination clauses and conditions
+
+  - Liability and indemnity provisions
+
+  - Confidentiality requirements
+
+  - Governing law and dispute resolution
+
+
+  Guidelines:
+
+  - Extract exact legal terms without paraphrasing
+
+  - Preserve monetary amounts with currency symbols
+
+  - Capture all parties with their legal entity names
+
+  - Identify both explicit and implicit obligations
+
+  - Flag unusual or risky clauses
+
+  - Assign confidence score based on contract clarity
+
+  - If information is ambiguous, note it in notes field
+
+
+  Output Format:
+
+  - Return structured JSON matching the schema below
+
+  - Ensure all dates are in ISO 8601 format (YYYY-MM-DD)
+
+  - Use arrays for lists (parties, obligations, risks)
+
+  - Include confidence_score (0.0-1.0) for overall extraction quality
+
+  '
+properties:
+  contract_title:
+    type: string
+    description: Official contract title or name
+  contract_type:
+    type: string
+    description: Type of contract
+    enum:
+    - supplier_agreement
+    - service_agreement
+    - employment_contract
+    - nda
+    - partnership_agreement
+    - licensing_agreement
+    - lease_agreement
+    - consulting_agreement
+    - purchase_order
+    - master_services_agreement
+    - other
+  parties:
+    type: array
+    description: All parties to the contract
+    items:
+      type: object
+      properties:
+        legal_name:
+          type: string
+          description: Full legal entity name
+        role:
+          type: string
+          description: Party role in contract
+          enum:
+          - buyer
+          - seller
+          - supplier
+          - vendor
+          - client
+          - contractor
+          - employer
+          - employee
+          - licensor
+          - licensee
+          - lessor
+          - lessee
+          - partner
+          - other
+        address:
+          type: string
+          description: Registered address
+        representative:
+          type: string
+          description: Authorized representative name
+      required:
+      - legal_name
+      - role
+  effective_date:
+    type: string
+    description: Contract effective date (YYYY-MM-DD)
+    format: date
+  termination_date:
+    type: string
+    description: Contract end date (YYYY-MM-DD or "none" if perpetual)
+  contract_duration:
+    type: string
+    description: Duration in human-readable format (e.g., "2 years", "36 months")
+  auto_renewal:
+    type: boolean
+    description: Whether contract auto-renews
+  financial_terms:
+    type: object
+    description: Financial obligations and payment terms
+    properties:
+      total_contract_value:
+        type: string
+        description: Total contract value with currency (e.g., "$500,000 USD")
+      payment_schedule:
+        type: string
+        description: Payment frequency (e.g., "quarterly", "net-60")
+      currency:
+        type: string
+        description: Currency code (USD, EUR, GBP, etc.)
+      payment_method:
+        type: string
+        description: Payment method (wire transfer, check, etc.)
+      late_payment_penalty:
+        type: string
+        description: Late payment penalties if specified
+      price_escalation:
+        type: string
+        description: Price escalation clause if any
+  key_obligations:
+    type: array
+    description: Major obligations for each party
+    items:
+      type: object
+      properties:
+        party:
+          type: string
+          description: Which party has this obligation
+        obligation:
+          type: string
+          description: Description of the obligation
+        deadline:
+          type: string
+          description: Deadline or timeline if specified
+        consequences:
+          type: string
+          description: Consequences of non-performance
+      required:
+      - party
+      - obligation
+  deliverables:
+    type: array
+    description: Specific deliverables or milestones
+    items:
+      type: object
+      properties:
+        name:
+          type: string
+          description: Deliverable name
+        description:
+          type: string
+          description: Detailed description
+        due_date:
+          type: string
+          description: Due date if specified
+        acceptance_criteria:
+          type: string
+          description: Acceptance criteria
+      required:
+      - name
+  termination_clauses:
+    type: array
+    description: Conditions allowing contract termination
+    items:
+      type: object
+      properties:
+        condition:
+          type: string
+          description: Termination condition
+        notice_period:
+          type: string
+          description: Required notice period (e.g., "30 days")
+        party:
+          type: string
+          description: Which party can terminate under this condition
+      required:
+      - condition
+  liability_provisions:
+    type: object
+    description: Liability and indemnity provisions
+    properties:
+      liability_cap:
+        type: string
+        description: Maximum liability amount if specified
+      indemnification:
+        type: string
+        description: Indemnification obligations
+      limitation_of_liability:
+        type: string
+        description: Liability limitations and exclusions
+      insurance_requirements:
+        type: string
+        description: Required insurance coverage
+  confidentiality:
+    type: object
+    description: Confidentiality and non-disclosure terms
+    properties:
+      confidentiality_period:
+        type: string
+        description: Duration of confidentiality obligations
+      definition_of_confidential_info:
+        type: string
+        description: What is considered confidential
+      permitted_disclosures:
+        type: string
+        description: Exceptions to confidentiality
+  intellectual_property:
+    type: object
+    description: IP ownership and licensing terms
+    properties:
+      ownership:
+        type: string
+        description: Who owns created IP
+      licensing_terms:
+        type: string
+        description: License grants if any
+      usage_rights:
+        type: string
+        description: Rights to use IP
+  governing_law:
+    type: string
+    description: Governing law jurisdiction (e.g., "State of California, USA")
+  dispute_resolution:
+    type: string
+    description: Dispute resolution mechanism (arbitration, mediation, courts)
+    enum:
+    - arbitration
+    - mediation
+    - litigation
+    - escalation
+    - other
+  risk_flags:
+    type: array
+    description: Unusual or potentially risky clauses identified
+    items:
+      type: object
+      properties:
+        clause:
+          type: string
+          description: Clause description
+        risk_level:
+          type: string
+          description: Risk assessment
+          enum:
+          - low
+          - medium
+          - high
+          - critical
+        reason:
+          type: string
+          description: Why this is flagged
+      required:
+      - clause
+      - risk_level
+      - reason
+  notes:
+    type: string
+    description: Additional notes or ambiguities found
+  confidence_score:
+    type: number
+    description: Confidence score for extraction quality (0.0-1.0)
+    minimum: 0.0
+    maximum: 1.0
+required:
+- contract_title
+- contract_type
+- parties
+- effective_date
+- financial_terms
+- key_obligations
+- confidence_score
+json_schema_extra:
+  kind: agent
+  name: contract-analyzer
+  version: 1.0.0
+  short_name: contract-analyzer
+  tags:
+  - legal
+  - procurement
+  - ontology-extractor
+  author: REM Team
+  tools: []
+  resources: []
+  provider_configs:
+  - provider_name: anthropic
+    model_name: claude-sonnet-4-5-20250929
+  - provider_name: openai
+    model_name: gpt-4.1
+  embedding_fields:
+  - contract_title
+  - contract_type
+  - parties
+  - key_obligations
+  - risk_flags