Comment by item007

This is really helpful detail — and I think your Airtable description nails the core: the value isn’t “having tasks”, it’s having a workflow that progressively turns vague items into schedulable commitments, plus capacity constraints so you don’t lie to yourself about time.

On the LLM point, I agree with your hesitation. For anything that touches real people/projects, the default needs to be privacy-first: either local-only, or scoped so the model never needs sensitive identifiers. One approach I’m exploring is separating “private entities” from “public knowledge”: let the system operate on generic project states and action types, and only you see the real names. Another is: no pushy assistant at all—just a pull-based daily view that helps you move buckets forward with the workflow you already trust.

If you had to pick one improvement that doesn’t require sharing sensitive context, would you want:

1. better workflow scaffolding (turn uncategorized into scheduled + estimated + bucketed faster), or

2. a way to attach lightweight “done/decision logs” back to tasks so the graveyard stops growing?

Details in my HN profile/bio if you’re curious what I’m validating.