copiloto-arch

Consolidate canonical AI architecture and ADR decisions for Copiloto development.

Updated May 14, 2024
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill copiloto-arch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: copiloto-arch
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/jana-arch
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill copiloto-arch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the need to repeatedly re-read many project ADRs by providing a single, canonical reference for how the Copiloto (Jana) AI architecture is structured and operated.

Core Features & Use Cases

  • Canonical Copiloto architecture snapshot: covers the current production stack, memory layers, embeddings, metrics, and telemetry conventions.
  • Decision-to-implementation alignment: summarizes key ADRs (0035–0053) so changes stay consistent with governance and design constraints.
  • Implementation patterns for safety and tenant isolation: enforces multi-tenant business_id scoping, LGPD/PII handling, and append-only memory + metrics practices.

Use case example: when adding or debugging an Agent in Modules/Copiloto (e.g., ChatCopilotoAgent), use this Skill to confirm which driver stack, memory context angles, telemetry attributes, and multi-tenant rules must be followed.

Quick Start

Ask the AI: “Using the copiloto-arch skill, propose the correct place in Modules/Copiloto to implement this change, and list the required components, tenant rules, metrics updates, and relevant ADR constraints.”

Frequently Asked Questions about copiloto-arch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce multi-tenant data isolation in a Laravel AI architecture?

Multi-tenant isolation in a Laravel AI architecture is enforced by strictly scoping all queries and memory operations using a business_id. This prevents cross-tenant data leakage while maintaining append-only memory semantics.

What is the canonical way to instrument OpenTelemetry GenAI events for an AI agent?

Instrumenting OpenTelemetry GenAI events requires applying standardized telemetry conventions to capture AI agent execution attributes. This provides operational visibility into agent performance and contextual tracing within the ERP system.

How do I configure Meilisearch for hybrid search in a multi-tenant ERP?

Configuring Meilisearch for hybrid search involves integrating the search engine with the Laravel AI stack to handle vector and textual queries. This setup must respect tenant boundaries and align with established architectural decision records.

Does my Laravel AI application need LGPD redaction for agent memory?

LGPD redaction is required for agent memory in your Laravel AI application to ensure Personally Identifiable Information is masked. This compliance step must be applied before appending data to memory layers or emitting telemetry metrics.

What are the limitations of append-only memory in AI agent development?

The limitation of append-only memory in AI agent development is that historical context cannot be updated or deleted, requiring strict data hygiene at ingestion. This constraint guarantees audit trails but demands careful PII redaction beforehand.