{
    "$schema": "https://schema.stn-labz.com/site/v1/schema.json",
    "version": "1.0",
    "site": {
        "url": "https://chaos-mvc.org",
        "name": "Chaos MVC",
        "description": "Lightweight Model View Controller",
        "language": "en"
    },
    "resources": [
        {
            "url": "https://chaos-mvc.org/announcements",
            "type": "other",
            "title": "Announcements",
            "description": "The Public announcements module for the ChAoS MVC",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/bugs",
            "type": "other",
            "title": "Bugs",
            "description": "Chaos MVC domain module: bugs",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/capabilities",
            "type": "other",
            "title": "Capabilities",
            "description": "ChAoS MVC Capibilities Overviews",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/certification",
            "type": "other",
            "title": "Certification",
            "description": "Chaos MVC domain module: certification",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/changelog",
            "type": "other",
            "title": "Changelog",
            "description": "Changelog Module for the ChAoS MVC",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/chaos-mvc-1-2-1",
            "type": "page",
            "title": "ChAoS MVC 1.2.1",
            "description": "ChAoS MVC 1.2.1 introduces the filesystem-backed Pages system, expanded Markdown rendering, modernized search-engine and machine-readable discovery, RSS support, and a schema-validated Site Resource Declaration.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/codex",
            "type": "other",
            "title": "Codex",
            "description": "Chaos MVC domain module: codex",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/contact",
            "type": "other",
            "title": "Contact",
            "description": "A website contact utility module that uses the Chaos MVC built-in mailer to capture and manage contacts from the domain.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/developers",
            "type": "other",
            "title": "Developers",
            "description": "Chaos MVC developer profiles, slug-based public profiles, public signing keys, certification lifecycle, and complete module/data lifecycle management.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/docs",
            "type": "other",
            "title": "Documentation",
            "description": "Filesystem-backed Markdown documentation browser for Chaos MVC.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/downloads",
            "type": "other",
            "title": "Downloads",
            "description": "Chaos MVC domain module: downloads",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/example",
            "type": "other",
            "title": "Example",
            "description": "Canonical ChAoS MVC user Module reference for MVC structure, Module and Data Lifecycles, Data Reset, and complete CRUD.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/forge",
            "type": "other",
            "title": "Forge",
            "description": "Developer submission, review, certification, marketplace, and data lifecycle management for Chaos MVC.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/foundation",
            "type": "page",
            "title": "The ChAoS Foundation",
            "description": "Supporting Open Source Beyond the Present",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/github",
            "type": "other",
            "title": "Github",
            "description": "Chaos MVC domain module: github",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/home",
            "type": "other",
            "title": "home",
            "description": "The home module for the ChAoS MVC, supersedes the absence of /home in the core",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/letters",
            "type": "other",
            "title": "letters",
            "description": "A standalone opt-in newsletter and distribution module for Chaos MVC.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/manifesto",
            "type": "other",
            "title": "Manifesto",
            "description": "Chaos MVC domain module: manifesto",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/patch-requirements",
            "type": "page",
            "title": "Patch Requirements",
            "description": "Requirements before ChAoS MVC Patching Occurs",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/policies",
            "type": "other",
            "title": "Policies",
            "description": "Chaos MVC domain module: policies",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/posts",
            "type": "page",
            "title": "Posts",
            "description": "Posts",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/posts/chaos-mvc-modules",
            "type": "article",
            "title": "ChAoS MVC Modules",
            "description": "# Now Own Their Database Lifecycle As the ChAoS MVC module ecosystem continues to grow, we're tightening up one of the areas that has traditionally made module installation unnecessarily messy: **database setup.** Going forward, SQL-backed ChAoS MVC modules will be expected to manage their own database requirements rather than relying on developers or administrators to manually import `.sql` files. ## No More Manual SQL Installation If a module requires its own database table, the module should be able to determine whether that table exists and provide an administrator-controlled way to configure it. The expected flow is simple: ```text Install Module ↓ Module Detects Missing Table ↓ Admin Opens Module ↓ Configure Module ↓ Module Creates Its Own Tables ↓ Module Verifies Configuration ↓ Ready ``` Installing a module does **not** automatically mean executing SQL. Instead, an SQL-backed module can expose a **Configure Module** action through its administrative interface. The administrator explicitly invokes that action, and the module creates the database resources it owns. This keeps database changes visible and intentional. ## Modules Own Their Tables Database ownership is now an important part of the module contract. If a module creates a table, that table belongs to that module. For example, the Short URL module owns: ```text short_urls ``` The companion `/s` redirect module can use that table to resolve links and record redirect activity, but it does not own the table. That means: ```text short_url ├── creates short_urls ├── configures short_urls ├── manages short_urls └── may remove short_urls during uninstall s ├── reads short_urls ├── updates redirect statistics └── NEVER creates or removes short_urls ``` This distinction becomes especially important as modules begin working together. Using another module's data does not establish ownership of that data. ## Uninstall Should Complete the Lifecycle We're also looking at extending the module lifecycle so modules can cleanly remove resources they own. The lifecycle would become: ```text Install ↓ Configure ↓ Operate ↓ Uninstall ``` When ChAoS MVC invokes something such as: ```php $admin->unInstall(); ``` a module could expose its own uninstall handler to perform module-specific cleanup. For an SQL-backed module, that could include removing tables that the module explicitly owns. Conceptually: ```php public function uninstall(): bool { // Remove resources owned exclusively by this module. return true; } ``` The framework handles the uninstall lifecycle. The module knows what belongs to it. ## Uninstall Must Respect Ownership An uninstall routine should not become a license to start deleting things. A module may remove: ```text its own tables its own persistent module data its own generated resources ``` It should not remove: ```text Core tables another module's tables shared resources it does not own unrelated user data ``` That gives us a very simple rule: > **A module can clean up what it created and owns.** This also means dependent or companion modules cannot destroy shared resources simply because they use them. If `/s` were uninstalled, for example, the `short_urls` table remains untouched. If the owning Short URL module is explicitly uninstalled with database cleanup enabled, *then* removal of that table can be part of its uninstall process. ## Preserve Data When Appropriate Removing a module and destroying its data do not necessarily need to mean the same thing. An administrator may want to uninstall and later reinstall a module without losing its existing data. For that reason, destructive database cleanup should be an explicit administrator decision. The uninstall process could provide an option such as: ```text ☐ Remove module data and database tables ``` The framework could then invoke the module uninstall process with that decision: ```php $module->unInstall($removeData); ``` If module data removal is not requested, the module files can be removed while its persistent data remains available for a future reinstall. If module data removal is explicitly requested, the module may remove the database resources and persistent data that it owns. The module owns its data lifecycle. The administrator decides when destruction is appropriate. ## Why This Matters The goal is to make ChAoS MVC modules genuinely portable. A developer should eventually be able to distribute a module without telling users: > Install the module, open phpMyAdmin, find this SQL file, import it, make sure you selected the right database, and then come back. That's not a module installation process. That's homework. A properly packaged module should understand its own requirements. The administrator decides when configuration happens. The module performs the configuration it owns. And when the module is deliberately removed, it can clean up the resources it owns. ## The Emerging Module Contract This gives ChAoS MVC modules a much clearer lifecycle: ```text MODULE │ ├── module.json │ ├── controllers/ │ ├── models/ │ ├── views/ when required │ ├── docs/ │ └── CHANGELOG.md │ ├── Configuration │ └── module-owned database setup │ └── Uninstall └── module-owned resource cleanup ``` Not every module needs SQL. Not every module needs a public view. Not every module needs the same directory structure. What every module does need is a clear understanding of **what it owns**. That's becoming one of the central rules of ChAoS MVC module development: **Install what you own. Manage what you own. Remove what you own. Leave everything else alone.**",
            "language": "en",
            "index": true,
            "published": "2026-08-31"
        },
        {
            "url": "https://chaos-mvc.org/posts/chaos-mvc-supports-ror",
            "type": "article",
            "title": "Chaos MVC supports RoR",
            "description": "We here at Chaos, support the usage of [RoR](https://rorweb.com/) because it helps legacy Search Engines learn. It also helps AI learn, by including it in the `llms.txt` that AI use, they learn to see the output of `ror.xml` and then learn how to crawl, based on its content. With this, **Chaos** fully supports **RoR**.",
            "language": "en",
            "index": true,
            "published": "2026-03-16"
        },
        {
            "url": "https://chaos-mvc.org/posts/chaos-mvc-v-1-2-1-released",
            "type": "article",
            "title": "ChAoS MVC v 1.2.1 Released",
            "description": "**Release Date:** September 19, 2026 **Release Type:** Security and Core Feature Release [Download ChAoS MVC 1.2.1](https://github.com/stnlabz/chaos-mvc/releases/tag/1.2.1) --- ## Build More. Fight the Framework Less. ChAoS MVC 1.2.1 is a major step forward for building real websites with ChAoS. This release introduces built-in Pages, greatly expanded Markdown support, RSS feeds, improved search-engine discovery, and a machine-readable Site Resource Declaration. You can now create traditional website Pages directly in ChAoS, publish rich Markdown content, automatically expose public content to search engines and other discovery systems, and keep your installation's content safely separated from the protected Core. Already running ChAoS MVC 1.2.0? Your Core Updater can take care of the upgrade. New to ChAoS? Welcome. 1.2.1 gives you considerably more to build with. --- ## Pages Are Here Not everything belongs in a Module. Sometimes you just need a page. ChAoS MVC 1.2.1 introduces a filesystem-backed Pages system for creating content such as: - About pages - Documentation - Policies - Project information - Landing pages - Contact information - Other permanent website content Pages get clean URLs: /about-us /documentation /our-project And you can write them using: - Markdown - HTML - Plain text - JSON Pages support draft and published states, Admin editing, theme-aware rendering, slug changes, recoverable deletion, and automatic discovery by supported ChAoS resources. Your Pages live under `/user/pages`, keeping your content separate from the protected ChAoS Core. --- ## Markdown Got a Serious Upgrade If you like writing in Markdown, 1.2.1 is a good release for you. ChAoS now supports a much richer Markdown vocabulary, including: - Headings - Bold and italic text - Strikethrough - Code and fenced code blocks - Links and automatic URL linking - Blockquotes - GitHub-style alerts - Ordered and unordered lists - Nested lists - Task lists - Tables - Definition lists - Footnotes - Escaped Markdown characters - Controlled small text - Allowlisted named colors That makes Markdown useful for far more than simple Posts. Documentation, research, project pages, technical writing, and long-form content can all remain readable in source form while rendering cleanly on your site. ChAoS continues to escape raw source HTML before transforming supported Markdown, and unsafe URL schemes remain rejected. --- ## Your Site Is Easier to Discover Publishing something shouldn't mean manually updating five different discovery files. ChAoS 1.2.1 modernizes its discovery system so supported resources can automatically find public content across your installation. That includes: - Public Core routes - Public user Modules - Published Pages - Published Posts where applicable ChAoS can use that information to maintain: sitemap.xml ror.xml rss.xml llms.txt site.json Add something public to your site, refresh your indices, and ChAoS does the bookkeeping. --- ## RSS Is Now Built In ChAoS MVC now includes Core RSS support for published Posts. Your site can provide a standard RSS feed with stable post URLs and XML-safe content, including presentation support through the included RSS stylesheet. For site owners, that means another discovery and subscription mechanism is available without requiring an additional Module. --- ## Meet `site.json` ChAoS MVC 1.2.1 introduces a machine-readable Site Resource Declaration. `site.json` describes the installation and its public resources using a defined schema, giving machines a predictable way to understand what a ChAoS site exposes. Declarations are validated against the STN-Labz Site Schema before publication. Remote schema data is used strictly for validation and receives no executable authority inside ChAoS. The 1.2.1 security review also tightened this system so public requests consume the existing validated declaration rather than repeatedly regenerating it. --- ## Your Stuff Stays Yours One of the most important ChAoS boundaries remains unchanged: **Updating ChAoS does not mean replacing your website.** The 1.2.1 Core update preserves installation-owned content, including your: - Modules - Themes - Pages - Public assets - Site configuration - Installation data The distributed Core remains separate from the things that make your installation yours. There is also **no database migration required** for 1.2.1. --- ## The Stock Modules Got Some Attention Too The included Home and Example Modules were reviewed as part of the 1.2.1 release process. Home remains the simple public starting point for a ChAoS installation. Example remains the reference Module for developers and demonstrates the current ChAoS Module lifecycle, including: - MVC structure - Public and Admin routing - CSRF-protected changes - Database lifecycle handling - Schema installation and migration - CRUD operations - Data reset and deletion - Input validation - Escaped output If you're learning to build ChAoS Modules, Example is there specifically to be taken apart. --- ## Already Running ChAoS MVC 1.2.0? Updating is straightforward. Go to: Admin → Core Updater The updater verifies the release and package, protects installation-owned files, creates a previous-Core snapshot, installs the new Core, and verifies the result. If installation fails, the previous Core can be restored. As always, keep a current external backup before updating production software. --- ## New to ChAoS MVC? ChAoS MVC is a lightweight PHP MVC framework built around a simple idea: **The Core provides the framework. Your installation belongs to you.** Start with the framework, choose or build a Theme, create Pages, add Modules when you need application behavior, and extend the installation without turning every website feature into Core code. ChAoS MVC 1.2.1 gives that model considerably more room to grow. [Download ChAoS MVC 1.2.1](https://github.com/stnlabz/chaos-mvc/releases/tag/1.2.1) --- ## For Developers Want the technical details? - [Developer Documentation](https://github.com/stnlabz/chaos-mvc/tree/1.2.1/docs) - [Module Creation Guide](https://github.com/stnlabz/chaos-mvc/blob/1.2.1/docs/MODULE_CREATION_GUIDE.md) - [Theme Documentation](https://github.com/stnlabz/chaos-mvc/blob/1.2.1/docs/THEMES.md) - [Full Changelog](https://github.com/stnlabz/chaos-mvc/blob/1.2.1/docs/CHANGELOG.md) The complete technical change record remains available in the ChAoS MVC documentation.",
            "language": "en",
            "index": true,
            "published": "2026-09-19"
        },
        {
            "url": "https://chaos-mvc.org/posts/the-retirement-of-the-chaos-cms",
            "type": "article",
            "title": "The Retirement of the Chaos CMS",
            "description": "#Chaos CMS is being retired. The project served its purpose. It provided a practical content-management platform, supported the development and operation of multiple web properties, and—perhaps most importantly—provided the experience that ultimately shaped what came next. ##That successor is Chaos MVC. The transition from CMS to MVC was not driven by a failure of Chaos CMS. It came from a change in engineering requirements. As the applications built around Chaos became more specialized, a traditional content-management system increasingly carried functionality and complexity that those applications simply did not require. **Chaos MVC takes the opposite approach.** It provides a much smaller application foundation built around separation of concerns and leaves application-specific capabilities where they belong: outside the core. The result is a smaller architecture, a reduced maintenance surface, and considerably more freedom to build applications around their actual requirements rather than around the assumptions of a general-purpose CMS. **There is also an important engineering lesson in the transition.** Software does not need to remain in production forever to have been successful. Sometimes a system completes the mission it was designed for. Experience gained from operating it exposes better architectural choices, requirements evolve, and the correct engineering decision becomes retirement rather than indefinite maintenance. **That is where Chaos CMS stands today.** The final **Chaos CMS** release is **Chaos Core v2.0.9**. The chaoscms.org domain will receive no further operational development and will be allowed to expire naturally. **Development continues with Chaos MVC**. `Chaos CMS → mission complete. Architecture evolved → MVC. Domain → no further operational requirement → natural expiration`.",
            "language": "en",
            "index": true,
            "published": "2026-08-14"
        },
        {
            "url": "https://chaos-mvc.org/posts/v1-1-6-released",
            "type": "article",
            "title": "v1.1.6 Released",
            "description": "Version 1.1.6 is live in the Downloads, it comes with the `core + admin` and an `installer` as well as a copy of the `developers portal` for those who love to `code` , version 1.1.7 is being planned.",
            "language": "en",
            "index": true,
            "published": "2026-03-19"
        },
        {
            "url": "https://chaos-mvc.org/posts/v1-1-7-released",
            "type": "article",
            "title": "v1.1.7 Released",
            "description": "Version 1.1.7 is live in the Downloads. ## It Adds - Module updating from within `admin`->`modules` This **release** follows the natural rythmic cycle of **Chaos**.",
            "language": "en",
            "index": true,
            "published": "2026-03-23"
        },
        {
            "url": "https://chaos-mvc.org/posts/v1-1-8-released",
            "type": "article",
            "title": "v1.1.8 Released",
            "description": "# v1.1.8 Release August 24, 2026 ## Added -Registration route /register → auth → register - Full registration flow integrated with accounts_model::create($data) - Email address update functionality in admin accounts ## Fixed - Admin account creation not submitting (routing + POST handling) - Inconsistent controller-to-model data handling - Broken signup method (now model-compliant) - Session messaging not displaying reliably in account actions - Admin account deletion incorrectly reporting \"You cannot delete your own account\" when deleting other accounts - Account deletion routing corrected so Admin → Accounts uses the intended account deletion handler (closes #f145ac) ## Changed - Standardized all account operations to array-based model input - Enforced role assignment via user_level (1 = user, 9 = admin) - Updated all registration forms to match new routing - Refactored authentication controller for consistent MVC flow ## Cleaned - Enforced PSR-12 formatting across accounts and auth systems - Added DocBlock coverage to controllers and models - Standardized database queries to positional bindings (?) - Removed inconsistent AI-generated logic and patchwork code. ## Notes - v1.1.7 focused on modules - v1.1.8 focuses on security",
            "language": "en",
            "index": true,
            "published": "2026-08-26"
        },
        {
            "url": "https://chaos-mvc.org/posts/v1-1-9-is-released",
            "type": "article",
            "title": "v1.1.9 is Released",
            "description": "# Chaos MVC 1.1.9 is Released After five months of development and security updates, **Chaos MVC 1.1.9 is now available**. ## Security Version 1.1.9 includes the security work completed over the past five months, with the changes focused on Core-owned functionality and strengthening the framework's boundaries. **User vs. Core Separation** Chaos MVC now has a clearer separation between the framework and the installation: ```text /user/ Installation-owned modules, themes, and data /app/ Chaos MVC Core ``` This separation reinforces one of the central principles behind Chaos MVC: **Protect the core. Grow outward**. ## What's Next? **Chaos MVC 1.1.10 is currently in development**. Development is focused on the next round of maintenance and update capabilities while 1.1.9 remains the current stable release. ## Download Chaos MVC 1.1.9 Visit [Downloads](/downloads) to grab the latest release: **Chaos MVC 1.1.9**.",
            "language": "en",
            "index": true,
            "published": "2026-08-31"
        },
        {
            "url": "https://chaos-mvc.org/posts/v1-2-0-is-released",
            "type": "article",
            "title": "v1.2.0 is Released",
            "description": "# ChAoS MVC 1.2.0 ChAoS MVC 1.2.0 establishes the finalized separation between framework-owned Core files and installation-owned user content. This release also introduces a rebuilt Core updater, complete module and theme update lifecycle improvements, stronger release verification, and additional security maintenance. ## Core Updater The Core updater now: - Updates only framework files under `/app`. - Never modifies `/user` or `/public`. - Preserves installation-owned `app/core/config.php`. - Preserves `app/data` and `app/views/public`. - Removes obsolete Core files during replacement. - Verifies every staged and installed Core file against the release manifest. - Rejects files outside the authorized Core boundary. - Rejects external database-migration payloads. - Retains exactly one previous Core snapshot. - Provides authenticated, CSRF-protected Core rollback. - Automatically restores the previous Core when installation fails. - Keeps Admin accessible while updater maintenance mode is active. - Reports early manifest failures instead of leaving progress frozen. - Requires generated releases to contain all boot-critical framework files. Core release packages are produced and published exclusively by chaos-mvc.org. ## Module Updates Module maintenance now includes: - Signed package verification. - RSA-SHA256 and OpenPGP publisher verification. - SHA-256 package-integrity verification. - Locally pinned publisher trust. - HTTPS update-source enforcement. - Authorized package-host validation. - Whole-directory staged replacement. - Removal of obsolete module files. - One previous filesystem snapshot. - Automatic restoration when activation fails. - Manual module rollback. - Signed, version-specific module database migrations. - Module-owned database-table confinement. - Durable migration replay prevention. - Transactional module removal and Nuke recovery. - Accurate `Up to date`, `Update available`, and failure reporting. Modules without a public `admin()` method no longer appear in site administration. ## Theme Updates Themes now use the same general update lifecycle as modules: - Remote version discovery. - Signed release verification. - RSA-SHA256 and OpenPGP support. - SHA-256 package verification. - Locally pinned publisher identity. - Staged whole-theme replacement. - Archive path and size validation. - Required theme-part validation. - PHP syntax validation before activation. - Automatic recovery from failed activation. - One previous theme snapshot. - Manual theme rollback. - Active-theme preservation during updates. Theme packages cannot contain SQL migrations or claim database ownership. ## User-Land Separation This release strengthens the boundary between Core and user-land components: - User modules are loaded from `/user/modules`. - User themes are loaded from `/user/themes`. - Core controllers retain routing priority. - Service modules can receive declared index parameters. - One-character module slugs are supported. - Module models and views resolve inside their established module context. - User-land code does not automatically inherit unrestricted Core authority. - Domain-specific modules and themes remain outside Core updates. ## Themes and Administration - Administrators can upload, select, and apply user themes. - Site administration inherits the active site theme. - Core header, navigation, and footer files remain available as fallbacks. - Theme metadata and update-source errors are reported accurately. - The Admin dashboard displays the installed ChAoS MVC Core version. ## Security Security maintenance includes: - Rejection of comments targeting unpublished posts. - Strengthened module class-ownership checks. - Confined archive extraction. - Rejection of path traversal and symbolic-link archive entries. - Portable filename and case-collision checks. - Bounded manifest, package, archive-entry, and expanded-file sizes. - Public-address validation for update servers. - TLS peer-name verification. - Rejection of redirects during module and theme package retrieval. - Publisher-key pinning. - Rejection of checksum-only publisher authentication. - Isolated OpenPGP verification keyrings. - Authentication throttling support. - Improved output handling in affected views. - Safer module filesystem and database lifecycle operations. ## Maintenance and Error Handling - Core error handling is registered during bootstrap. - Framework errors render through the site instead of generic browser pages. - Maintenance mode can be enabled or disabled through Site administration. - Updater maintenance does not block administrator recovery routes. - Logout uses POST and CSRF protection and returns users to `/`. - Optional Sentinel perimeter inspection remains available when Sentinel is installed. - Installations without Sentinel continue normally. ## Release Compatibility - Target version: `1.2.0` - Oldest supported automatic-update version: `1.1.9` - Core database migration: none - PHP database schema changes: none Module database migrations remain independently controlled by their signed module packages. ## Updating Before updating: 1. Confirm the installation reports ChAoS MVC `1.1.9` or newer. 2. Back up installation-owned data as normal operational practice. 3. Open **Admin → Core Updater**. 4. Select **Update Now**. 5. Confirm that the installed Core reports `1.2.0`. 6. Verify the public site, Admin interface, active theme, modules, and assets. The updater retains one previous Core filesystem snapshot for rollback. ## Live Validation The corrected Core update pipeline was successfully exercised against live ChAoS MVC installations before release. ## Documentation This release includes expanded documentation for: - Module creation and lifecycle operations. - Theme update packages. - RSA-SHA256 release signing. - OpenPGP and RSA publisher verification. - Core, module, and theme rollback behavior. - Installation and ownership boundaries.",
            "language": "en",
            "index": true,
            "published": "2026-09-06"
        },
        {
            "url": "https://chaos-mvc.org/posts/what-is-markdown",
            "type": "article",
            "title": "What is Markdown",
            "description": "## Markdown is a lightweight, easy-to-read markup language used to format plain text, which can be converted into HTML for web publishing. It uses simple punctuation marks—like hashtags for headers or asterisks for bolding—to apply styling, allowing users to focus on content rather than complex formatting tools. **Key aspects of Markdown include**: - **Readability**: Raw Markdown files are designed to be easily readable, even without being converted to HTML. - **Portability**: Because it is plain text, Markdown works on any platform and is future-proof. - **Common Use**: It is widely used for website content, README files on GitHub, technical documentation, and in apps like the Chaos MVC. - **Simple Syntax**: Examples include using # Heading for titles, **bold** for emphasis, and - list for bullet points and more. `# text = h1` `## text = h2` `### text = h3` `**text** = strong/bold` `*text* = italic/empasized` and more... Replace **text** with your content Markdown was created as a simpler alternative to HTML, allowing for quick creation of formatted text without needing to write out full HTML tags. *This Post* was rendered by the **Chaos MVC** built in rendering platform.",
            "language": "en",
            "index": true,
            "published": "2026-03-19"
        },
        {
            "url": "https://chaos-mvc.org/redirects",
            "type": "other",
            "title": "Redirects",
            "description": "Manage exact-match HTTP redirects with administrator-controlled database setup.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/research",
            "type": "other",
            "title": "Research",
            "description": "JSON-backed research publication module for ChAoS MVC.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/roadmap",
            "type": "other",
            "title": "Roadmap",
            "description": "Chaos MVC domain module: roadmap",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/rss.xml",
            "type": "feed",
            "title": "Chaos MVC RSS",
            "description": "Chaos MVC RSS",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/s",
            "type": "other",
            "title": "Short URL Service",
            "description": "Resolve shortened URLs and redirect visitors to their destination.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/security",
            "type": "other",
            "title": "Security",
            "description": "Public cryptographic identity and observable site security capabilities",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/security_policy",
            "type": "other",
            "title": "Security Policy",
            "description": "Chaos MVC domain module: security_policy",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/short_url",
            "type": "other",
            "title": "Short URL",
            "description": "Create and manage shortened URLs for use with the Chaos MVC Short URL redirect service.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/site-json",
            "type": "page",
            "title": "Site Json Announcement",
            "description": "site.json is a machine-readable declaration of a website and the public resources it makes available.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/sites",
            "type": "other",
            "title": "Sites",
            "description": "Public directory of websites with registered Chaos MVC installations.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/support",
            "type": "other",
            "title": "Support Module",
            "description": "Support ticket management with public submission, ticket tracking, administrative replies, tier assignment, and escalation.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/system_capabilities",
            "type": "other",
            "title": "System Capabilities",
            "description": "Chaos MVC domain module: system_capabilities",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/updates",
            "type": "other",
            "title": "Updates",
            "description": "Chaos MVC domain module: updates",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/user-module-research",
            "type": "page",
            "title": "User Module Research",
            "description": "User Module Libraries Use Research",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/what-is-chaos-mvc",
            "type": "page",
            "title": "What is the Chaos MVC?",
            "description": "ChAoS MVC is a lightweight, modular PHP MVC framework designed around a protected Core architecture and an outward-growing application model.",
            "language": "en",
            "index": true
        },
        {
            "url": "https://chaos-mvc.org/what-is-forge",
            "type": "page",
            "title": "What is forge",
            "description": "Forge provides the submission path between a ChAoS developer's work and the review processes of the ChAoS MVC ecosystem.",
            "language": "en",
            "index": true
        }
    ]
}