AI assistants & workflow automation · Engineering case study

Lamp: Lamp Context & Action Architecture

Keep identity, conversation memory and tool authority separate while connecting the assistant to application workflows.

Inside Lamp.

Explore Lamp

The Colyf API derives the user's identity and institution scope from authentication. A closed tool catalog exposes only operations allowed for the current role and configured features.

When a supported change is proposed, the application stores a reviewable proposal tied to the user and institution. Confirmation dispatches through existing authenticated routes, where access and resource restrictions are checked again.

Private conversation threads and explicit preferences persist in PostgreSQL with user and institution isolation. Saved context is useful for continuity; it is never a replacement for authorization.

The workspace agent for Telegram, WhatsApp and Slack is a separate integration with its own storage and tool boundaries. Its Jira and host capabilities are not inherited by users of the Colyf assistant.

  • Authenticated identity and a closed tool catalog
  • User-confirmed proposals with normal application authorization
  • Separate private memory and integration boundaries

Continue exploring.

Have a related challenge?

Talk to The Code Lawyers