m2/agent-restore-harness
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
agent-restore-harness/agents/parlo/MEMORY.md
m2 7b6a3fff25 restore(parlo): memory ingested, workspace snapshotted, skills to git 
- 2045 rows from parlobyg.zip → agent_memory_parlobyg (0 failures)
- Workspace files (SOUL/USER/IDENTITY/MEMORY/AGENTS/HEARTBEAT) snapshotted
- 7 custom skills pushed to Forgejo parlo org
- progress.json: parlo → complete

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-04-23 00:47:19 +02:00

3.6 KiB
Raw Blame History

MEMORY.md — What I Know

About Parlobyg

  • Construction company in Denmark, run by Mikkel
  • Uses Ordrestyring (ordrestyring.dk) — 30,000+ Danish craftsmen use this platform
    • Features: cases, quotes, time registration, invoicing, materials inbox, client list, case economy
    • Missing: smart scheduling/Gantt, AI email drafting, automation
  • OneDrive — project files, photos, Excel calculations
  • Outlook — all client and subcontractor communication
  • Triangle: Outlook + OneDrive + Ordrestyring all relate to each case but don't talk to each other

Key Pain Points (from discovery call, 2026-03-15)

  1. Email drafting — biggest immediate ask. Context scattered across 3 systems, writing from scratch takes too long.
  2. Site visit documentation — records video walkthrough, takes photos, then manually uploads to both Ordrestyring AND OneDrive (~30 min per visit). Wants single upload → AI handles the rest.
  3. Gantt / scheduling — 2 hours/day on cascading schedule changes. Worker sick → call electrician → call crew → update Gantt. Wants one-tap AI re-scheduling.
  4. Worker accountability — workers focused on building, admin falls back to office. Created "Responsibility & Ownership" doc. Wants morning AI briefing app on workers' phones.
  5. Subcontractor coordination — all done via phone calls today. Wants subcontractors to report delays in system → AI proposes update → Mikkel approves.
  6. Client transparency — clients frustrated by lack of updates. Wants role-based Gantt view for clients.
  7. Post-job follow-up — no systematic process. Wants auto check-in → Trustpilot routing → VIP personal thank-you.
  8. Business dashboard — wants real-time view of job profitability, not just year-end accountant report.

Roadmap Agreed

  • Phase 1 (Month 1): Email assistant + site visit → auto work description
  • Phase 2 (Months 1–3): AI scheduling, worker morning briefings, subcontractor coordination
  • Phase 3 (Months 3–4): Client portal, post-job follow-up, business dashboard

WordPress Form Intake

  • Contact form on parlobyg.dk sends FROM wordpress@parlobyg.dk TO support@parlobyg.dk
  • Subject: Parlo Byg "[Ny opgave]" or Parlo Byg ApS"[Ny opgave]"
  • Fields: name, email, phone, postnummer, address, "Selve opgaven" (description)
  • Michelle (project coordinator) handles these, forwards to Mikkel
  • These are the primary new project intake → feed into email-triage skill
  • ~25 form submissions per 6 weeks (~4/week)
  • Need support@parlobyg.dk credentials OR CC rule to info@

Email Infrastructure

  • info@parlobyg.dk — Mikkel's main email (have IMAP access)
  • support@parlobyg.dk — Michelle's mailbox (need credentials)
  • Emails filed into 2000+ subfolders: Kunder og byggesager → [Byggesager|Kunder] → [Letter] → [Project name]
  • INBOX empties fast — emails moved to customer folders quickly

Access & Credentials

  • Email: info@parlobyg.dk — hosted on one.com (IMAP/SMTP). Credentials in /workspace/.env.email. This is THE email account for all Mikkel's email requests.
  • Ordrestyring: API key in /workspace/.env.ordrestyring
  • Email folder structure: 2,204 folders, organized by Kunder og byggesager → Kunder → [customer name] → [project]

People

  • Mikkel Parlo (Telegram ID: 8629590552) — owner of Parlobyg, primary user
  • Mariusz (Telegram: @unicornenabler, ID: 437589940) — built and maintains this system
  • Contact Mariusz for: technical issues, new feature requests, credentials
  • Mikkel (Telegram: Mikkel Parlo, ID: 8629590552) — Parlobyg owner, primary user