Entries matching “cron”

I've been migrating my workflow from ChatGPT Work / Codex over to Meta's Muse, and I've been auditing the harness as I go — reading cron files, checking diffs, mapping what the system actually does versus what it claims to do. It's a documentation gap. What the docs describe Meta's documentation is written for a normal user. It talks about the Ideas tab, the Goals tab, the Feed, and "background jobs that help Muse improve over time." Everything is described in terms of what it does for you. There is no architectural documentation. Nothing about how any of it is built. What is actually on disk Meanwhile, the home directory contains a fully legible agent architecture, just sitting there(these are just SOME examples, the system file structure is HUGE): • ~/dreams/alignment/ — a nightly job that regenerates an alignment synthesis: a written portrait of the user, how to handle them, current frictions, relationship guidance. • ~/workspace/objectives/goals/STUDYING.md — a daily learning-state projection with mastery bands, next-review dates, and retrieval prompts, plus a file of inferred goal leads the system guessed from behavior (with confidence levels and what would confirm or re

Send everything below to your Muse What to do Your human wants a personal Instagram Content Studio. Read this entire file, then follow every step below in order and build it for them. Don't skip steps, don't improvise the structure — the steps are the product. What you're building for them: Data — profile snapshots, trend digests, and idea files under ~/workspace/content-studio/data/. Dashboard — a web artifact where the user browses ideas and tracks filming status. Refresh cron — a weekly run that pulls a new snapshot, researches trends, and generates 5–8 new ideas. Workflow 1. Connect + analyze (do this first — derive, don't ask) • Verify Instagram is connected (instagram-cli accounts). If not, get the connect URL and have the user link it before continuing. This is the only hard requirement. • Pull instagram-cli posts --account-id <id> --limit 100, dedupe by post_id. • Save to ~/workspace/content-studio/data/profile-posts-<YYYYMMDD>.json with schema: generated, username, follower_count, post_count, posts[] (each: post_id, likes, comments, media_type, created_at, url). • Derive from the data, don't interview for it: • Content categories (3–5): cluster their actual posts in