Phuriwaj

Daily Journal — 2026-05-20

Freewrite

A day of dense AI tooling and integration work. The morning was spent connecting the pieces of the stack — Jira via Composio, Gmail connectors, email automation to Teams — while the afternoon circled back to bigger architectural questions: how to run Claude Code fully autonomously overnight, and whether MiniMax is actually safe to use for API workloads. The privacy analysis was a sobering read. Good to have clarity.

Big Things Today

  • Review and action Composio vs Atlassian MCP decision for Hermes Jira integration
  • Re-calculate Hermes gateway capacity model using 2–5× concurrent multiplier per agentic session
  • Validate CreditX persona demand and hour-based pricing with field conversations

Conversations

Product Strategy

CreditX

Explored CreditX — a new BOL product concept layered on top of CorpusX and TradeX for Corporate Credit Officers. Architecture and prototype are done. The product formalises work credit officers already do manually in spreadsheets. Key structural moat: once a company’s credit committee uses CreditX as its decision record, the audit trail becomes load-bearing and hard to migrate. Risks: persona demand unvalidated, hour-based pricing (฿2,250/hr) untested, Concentration Overlay depends on TradeX critical mass, backend decision-record build cost unsized. → See creditx

AI Tooling & Integrations

Jira Connection Setup

Created Jira task PT-1 successfully via Composio MCP. First live Jira task from Claude. Very short but meaningful milestone. → See composio-mcp-connector

Composio AI Agent Integration Platform

Discovered Rovo is blocked on personal Jira (phuriwaj.atlassian.net) because the account is registered with outlook.com — Atlassian restricts Rovo to business domains. Composio is the correct alternative; Atlassian’s own MCP with OAuth also bypasses this restriction. → See composio-mcp-connector

Testing Gmail Connector Email Delivery

Explored two paths for adding Gmail to Claude: Composio (manual MCP URL config) vs Zapier (one-click, in directory, 50 sends/month free). Zapier is simpler for casual use; Composio for agent-integrated workflows. → See composio-mcp-connector

Automation & Scripting

Power Automate Workflow URL Explanation

Built a Python email summary script using the O365 library (the OAuth2 replacement for Basic Auth, deprecated by Microsoft in 2022). Sends a Claude-generated digest to a Teams Adaptive Card on a daily cron. Azure App registration + Microsoft Graph permissions required. → See o365-email-teams-summary

Note Taking — Hugo & Quartz

Added crontab for sync-pkm.sh to auto-sync notes to Dockerised Quartz site on weekdays at 18:00. Confirmed Docker volume (dockerized-quartz_quartz-modules) and container (quartz-notes) are running correctly. → See quartz-pkm-setup

Claude Code Architecture

Messaging Claude Code on Discord and LINE

Claude Code Channels (v2.1.80+, --channels flag) natively supports Discord and Telegram. LINE not officially supported; community tool cc-connect (github.com/chenhg5/cc-connect) bridges to 11 platforms including LINE with no public IP needed. → See claude-code-channels

Evaluating Claude Code Automation Credibility

Reviewed Echofold article (Kevin Collins, Claude Ambassador) on autonomous dev pipelines. Credible technically but aspirational in framing. Most useful sections: Phase 3 (Hooks), Phase 9 (Agent SDK/session-per-ticket pattern), complete settings.json config reference. → See claude-code-autonomous-pipeline

CC-Autonomous

Deep dive into GSD + autonomous-dev harness as the gold-standard autonomous pipeline. Key differentiator: adversarial spec-blind reviewer (separate agent validates output without seeing implementation). Pipeline covers requirements → roadmap → plan → wave-based execution → hard gates (0 failures, no stubs, security scan) → verify → PR. GitHub Actions trigger pattern on requirements.md push is useful for Hermes. → See claude-code-autonomous-pipeline

Capacity & Security

API Rate Limits Explanation

Confirmed: 1 agentic Claude Code session ≈ 2–5 concurrent API requests (parallel tool calls). For Hermes gateway capacity planning with a 10-concurrent Z.ai limit, realistic user concurrency = 2–3 active agentic users, not 10.

Minimax Privacy Policy Data Training Concerns

Analysed MiniMax Open Platform Privacy Policy (2023). No “won’t train” clause. Rights explicitly reserved to use de-identified data commercially. Data stored in China. Compared against Z.ai (DPA embedded, Singapore storage, API data not retained). Decision: Z.ai preferred for any BOL or customer-sensitive workloads. → See minimax-security-privacy

Open Tasks Surfaced

  • Re-calculate Hermes gateway capacity model (1 session = 2–5 concurrent, not 1:1)
  • Evaluate GSD + autonomous-dev harness for Hermes overnight build pipeline
  • Set up Atlassian MCP server with OAuth as alternative to Composio for Jira
  • Test cc-connect if LINE integration for Claude Code becomes needed
  • Confirm approval status of MiniMax token procurement memo (recall was attempted 2026-05-19)
  • Register email MCP in Cowork MCP settings and test daily generator delivery
  • Run 3–5 field conversations with corporate credit officers to validate CreditX persona demand
  • Size backend build cost for CreditX decision-record feature

Insights Worth Developing