wp-new

To atomically register a new work product, you append synchronized entries to MEMORY, WP-REGISTRY, WeekPlan, Strategy mapping, and generate a templated inbox context file. This ensures numbering, budget, and acceptance criteria are consistently preserved across all project files.

Adding an unplanned task to a weekly plan requires a structured intake checklist to capture title, repo, budget, and priority. The process then validates integer ID sequencing, checks weekly budget constraints, and performs multi-file registration to prevent fragmented task onboarding.

Work product ID sequencing enforces integer-only IDs by finding the last integer WP number and explicitly rejecting lettered suffixes. This validation mechanism ensures strict numeric progression and prevents inconsistent naming conventions across the WP registry.

Yes, the task registration flow reads the WeekPlan to check weekly budget constraints before creating a work product. It warns about weekly budget overruns during the intake process, gating the atomic multi-file registration to prevent overspending.

You need to map a new work product to strategy mapping for RPs ≥3h when the task requires synchronized entries across project records. This happens during atomic multi-file registration, ensuring strategic alignment for work products with significant time investments.

Creating a templated inbox markdown file with frontmatter requires strict adherence to intake validation rules and integer ID sequencing. The process rejects lettered suffixes and depends on existing WeekPlan data to accurately gate weekly budget constraints and readiness criteria.