Changelog

The knowledge base now explains what a project is and how to start one, and the main internal projects are in the portfolio.

• How to run a project: a new projects guide sets out a three-step start. Install the LTP skill, let your AI agent interview you about the project, then write a short Summary covering objectives and key results, analysis, driver and timeline. Projects here are major internal efforts: a product, a process or a capability. Client work stays in client trackers.
• Four internal projects added: E2E Operators, E2E Hiring, PortalJS: Win Government Portal Customers and RFP Process Improvement now sit in the portfolio, with their analysis and supporting documents alongside them.
• Finance transformation removed: the AI Transformation of Finance & Operations initiative and its three finance projects have been removed from the portfolio.
• Cards for getting around: the homepage has two cards, Browse the portfolio and Start a project. The portfolio page is shorter, with live preview cards for the tree and map views. The navbar now links to Projects.

Screenshots from the Flowershow preview site.

The company portfolio now puts ongoing initiatives first, making it easier to see Datopian's products, internal systems, and current focus without wading through old campaigns and delivery plans.

A clearer starting view

The portfolio tree and map open with active initiatives only. The tree currently shows 11 active initiatives, organized under External Offers and Internal Systems. You can still explore projects and other statuses through the controls; owners remain visible without a separate owner-filter bar.

The updated portfolio tree, rendered locally from the repository.

Less stale material to navigate

• A smaller portfolio: the record set fell from 80 to 26 as empty, superseded, and retired standalone pages left the current portfolio.
• Initiatives carry the overview: 31 dated project records—including monthly marketing cycles, acquisition experiments, product demos, recurring practices, and completed internal rollouts—were retired from the portfolio. Useful outcomes, unresolved decisions, and execution links now sit on their initiatives; historical source records remain available for reference.
• A narrower role for projects: standalone company projects are reserved for bounded, core, cross-cutting work outside routine delivery. The company KB rollout and three finance infrastructure projects remain in that category. Two RFP improvement records stay visible while their implementation status is clarified.
• Obsolete content is removed: AI Data Answer material, old rebrand experiments, expired campaign calendars, duplicate launch drafts, personal backlogs and the superseded dashboard have been deleted from the repository. The discontinued Discord review workflow was removed, alongside unimplemented PortalSmith plans and two inactive finance ideas.
• Useful knowledge remains visible: CRM analysis, Queryless feedback, strategic context and operating guides are available as supporting knowledge. Publication exclusions now cover retained repository tooling and internal work records, rather than obsolete content collections.
• Uncertainty is visible: the retained records with expired commitments explicitly await owner review, rather than implying that an old deadline is still a current promise. The RFP improvement pages also flag disputed completion claims. Retiring a page does not declare its underlying work complete.

Simpler navigation

The homepage leads directly to the portfolio tree, with the map as an alternative. The navbar now gives quick access to Home, Portfolio, Changelog, and the KB Guide, and this changelog uses a chronological timeline with one page per update.

See the company portfolio, portfolio overview, or guide to the KB.