Activity
Mon
Wed
Fri
Sun
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
What is this?
Less
More
ship - mobile app founders

1.6k members • Free

Exit Plan Credit Repair

153 members • Free

JUSTANOTHERPM

1k members • Free

1 contribution to JUSTANOTHERPM
BWCC | Week 1 | Activity
Please share the following: 1. A screenshot of Claude Code running (doc 03) — and tell us which you picked, terminal or desktop app 2. Your CLAUDE.md (doc 04) 3. A screenshot of your front door script output (doc 05) — your real files, your real summaries 4. Your answer to this: what is the one workflow in your week that you'd hand to an agent tomorrow if you could? Be specific — not "admin", the actual thing. The Sunday night report. Chasing invoices. The weekly summary nobody reads. Deadline: Saturday noon. Post the broken ones too. If your install failed or your script threw an error, post the error. Someone else has hit it, or is about to. An error posted Thursday is a two-minute fix. The same error Sunday morning costs you the session. Read a few other people's CLAUDE.md files while you're here. Everyone's is different and you'll spot something yours is missing. I'm reading every post this week. Number 4 especially — I'll be pulling from your answers live on Sunday.
0 likes • Jul 19
Here's my Claude on Desktop. Can't use it on Terminal yet. Says cant find it. But I am planning to use it the App anyway.
0 likes • Jul 19
Below is my Second Brain info. Just copied what you provided. Going to change it as I get clearer on what I want. # Second Brain A personal system that knows what I know and what I'm doing. It ingests documents and connects to my calendar, email, and notes, then answers questions across all of it with citations back to the source — and eventually briefs me on my day. ## Status Greenfield — no code yet. This file exists to anchor the vision before implementation starts. ## Core idea One system, several sources of truth: - **Inbox folder** — documents dropped in for ingestion (PDFs, notes, articles, etc.) - **Calendar** — what's scheduled - **Email** — what's being communicated - **Notes** — what I've already written down Every answer the system gives should be traceable back to the specific source it came from (a document, an email, an event, a note) — no unsourced claims. ## Planned capabilities (roughly in order) 1. **Ingest** — watch/read the inbox folder, extract and index document content. 2. **Query with citations** — answer questions across ingested content, always pointing back to the originating source. 3. **Connect calendar, email, notes** — bring these in as additional queryable sources alongside documents. 4. **Daily brief** — proactively summarize the day ahead (schedule, relevant emails, open threads, notes) at a chosen time. ## Design principles - **Citations are non-negotiable.** Every synthesized answer must link back to source material. If a claim can't be traced, it shouldn't be stated as fact. - **Read-only against connected accounts** unless a feature explicitly requires write access (e.g., eventually drafting replies) — and that's opt-in, not default. - **Local-first where possible.** This holds personal data (documents, email, calendar); prefer local storage/indexing over sending everything to third-party services. - **Start with the inbox.** Get ingestion + citation-backed Q&A solid on static documents before wiring up live accounts — it's the smallest slice that proves the core loop.
1-1 of 1
Mohammed Real
1
5 points to level up
@mohammed-real-4714
AI Newbie

Active 4d ago
Joined Jul 12, 2026
Powered by