Release v0.12.0

FrameCode VibeWork v0.12.0 (Baseline)

This release provides the clean baseline of the FrameCode VibeWork (FCVW) framework, updated to V0.12.0 and ready for use in new projects. The main repository keeps the full history, but the attached ZIP is intended to start projects from scratch while preserving only the framework guidelines and removing local plan/session history.

What is new in this release:

• Declarative automation contracts: new Markdown-only governance contracts define pseudo-hooks, watcher rules, daemon loops, and governance gates without adding executable automation.
• ADR-0002: formalizes that hooks, watchers, daemons, and gates are documentation contracts in Scenario 1, not scripts or background processes.
• Output-token economy: TOKEN_BUDGET.md defines compact communication guidance so routine execution evidence stays in plans, changelogs, audits, troubleshooting records, release notes, and PR descriptions.
• Improved bilingual README: the README now explains the project clearly in PT-BR and EN-US, with Mermaid diagrams for the lifecycle, token economy, and declarative automation pipelines.
• README badge header: adds version, release, Apache 2.0 license, and LinkedIn contact badges.
• Apache 2.0 license: the framework license was moved to the repository root and aligned with Apache License 2.0.
• Clean V0.12.0 template: baseline package regenerated with the current version and without local plan/session history.

How to use:

1. Download the FrameCode-VibeWork-Clean-Template.zip file attached to this release.
2. Extract the contents into the root directory of your new repository or project under development.
3. Consult the AGENTS.md file and the FCVW/INSTANTIATION.md guide to start Phase 0 of your project.

---

Changelog V0.12.0

Version

V0.12.0

Date

2026-06-23

Release Status

published

GitHub Release Status

published

Release Type

minor

Summary

• Added Markdown-only declarative automation contracts for pseudo-hooks, watcher rules, manual/agentic daemon loops, and governance gates.
• Added ADR-0002 to clarify that hooks, watchers, daemons, and governance gates are governance contracts, not executable automation.
• Added TOKEN_BUDGET.md as the canonical output-token economy guidance for compact execution summaries.
• Refreshed the public README in PT-BR and EN-US with a clearer project explanation and Mermaid pipeline diagrams.
• Added a centered README badge header showing framework version, release, Apache 2.0 license, and LinkedIn contact.
• Moved the framework license to the repository root and changed the framework license posture to Apache License 2.0.
• Preserved conceptual credit to https://github.com/SantanderAI for declarative automation inspiration, without copying source code.

Related Plans

• FCVW/Plans/in_progress/P2-R3-2026-06-23-declarative-automation-contracts.md
• FCVW/Plans/in_progress/P2-R2-2026-06-23-v0120-communication-release.md

Note: these plans were still located in in_progress/ during release preparation because some cleanup/release-publication steps required manual follow-up.

Items Created

• LICENSE
• FCVW/AUTOMATION.md
• FCVW/HOOKS.md
• FCVW/WATCHERS.md
• FCVW/DAEMONS.md
• FCVW/GOVERNANCE_GATES.md
• FCVW/TOKEN_BUDGET.md
• FCVW/decisions/ADR-0002-declarative-automation-contracts.md
• FCVW/governance/TEMPLATE_AUTOMATION_CONTRACT.md
• FCVW/governance/TEMPLATE_HOOK_CHECK.md
• FCVW/governance/TEMPLATE_WATCHER_RULE.md
• FCVW/governance/TEMPLATE_DAEMON_LOOP.md
• FCVW/governance/TEMPLATE_GOVERNANCE_GATE_REPORT.md
• FCVW/wiki/sources/santanderai-declarative-automation-inspiration.md
• FCVW/changelogs/V0-12-0.md

Items Modified

• AGENTS.md
• README.md
• FCVW/AI.md
• FCVW/CONTEXT_MAP.md
• FCVW/FILESYSTEM.md
• FCVW/MANIFEST.md
• FCVW/SECURITY.md
• FCVW/STACK.md
• FCVW/WORKFLOW.md
• FCVW/skills/README.md
• FCVW/skills/governance-validator/SKILL.md
• FCVW/skills/wiki-lint/SKILL.md
• FCVW/wiki/index.md
• FCVW/wiki/log.md

Items Removed

• FCVW/LICENSE

Justifications

• The framework already optimized input-context consumption through selective loading, AICC session syntheses, and JIT skills. It also needed an explicit output-token economy rule to reduce unnecessary chat narration during governed execution.
• Declarative automation terminology needed to be made safe and unambiguous, preserving the pure Markdown baseline from ADR-0001 while allowing hooks, watchers, daemons, and gates to be documented as non-executable governance contracts.
• The public README needed to communicate the project more clearly to first-time readers, in both PT-BR and EN-US, with visual pipeline diagrams.
• The license needed to be placed at the repository root and aligned with Apache License 2.0 for free framework use.

Affected Files

• LICENSE
• AGENTS.md
• README.md
• FCVW/AI.md
• FCVW/AUTOMATION.md
• FCVW/CONTEXT_MAP.md
• FCVW/DAEMONS.md
• FCVW/FILESYSTEM.md
• FCVW/GOVERNANCE_GATES.md
• FCVW/HOOKS.md
• FCVW/MANIFEST.md
• FCVW/SECURITY.md
• FCVW/STACK.md
• FCVW/TOKEN_BUDGET.md
• FCVW/WATCHERS.md
• FCVW/WORKFLOW.md
• FCVW/changelogs/V0-12-0.md
• FCVW/decisions/ADR-0002-declarative-automation-contracts.md
• FCVW/governance/TEMPLATE_AUTOMATION_CONTRACT.md
• FCVW/governance/TEMPLATE_DAEMON_LOOP.md
• FCVW/governance/TEMPLATE_GOVERNANCE_GATE_REPORT.md
• FCVW/governance/TEMPLATE_HOOK_CHECK.md
• FCVW/governance/TEMPLATE_WATCHER_RULE.md
• FCVW/skills/README.md
• FCVW/skills/governance-validator/SKILL.md
• FCVW/skills/wiki-lint/SKILL.md
• FCVW/wiki/index.md
• FCVW/wiki/log.md
• FCVW/wiki/sources/santanderai-declarative-automation-inspiration.md

Functional Impact

• Adds compact output behavior as a first-class governance concern through TOKEN_BUDGET.md.
• Clarifies that detailed execution evidence should live in plans, changelogs, audits, troubleshooting records, release notes, and PR descriptions instead of being repeated in chat.
• Adds declarative automation contracts that let agents reason about pseudo-hooks, watchers, daemon loops, and gates without creating executable automation.
• Improves onboarding by making the README explain the project, lifecycle, token economy, and automation boundary visually and bilingually.

Visual Impact

• Adds a centered README header with shields/badges for:
  • framework version;
  • current release;
  • Apache 2.0 license;
  • LinkedIn contact.
• Adds Mermaid diagrams for:
  • main lifecycle pipeline;
  • token economy pipeline;
  • declarative automation pipeline.

Technical Impact

• Keeps FCVW as a Markdown-first governance framework.
• Does not add runtime code.
• Does not add package dependencies.
• Does not add CI/CD workflows.
• Does not install Git hooks.
• Does not create coded watchers.
• Does not create background daemons.
• Does not integrate provider SDKs or API-key flows.

License Impact

• Adds root-level LICENSE with Apache License 2.0 reference.
• Removes nested FCVW/LICENSE to avoid conflicting license placement.
• Establishes Apache 2.0 as the framework license posture.

External Inspiration Credit

Scenario 1 declarative automation records conceptual inspiration from https://github.com/SantanderAI, especially around:

• loop and stop-condition patterns;
• vault/lint style knowledge governance;
• hard-gate thinking;
• guardrail-oriented validation.

No SantanderAI source code was copied into FCVW.

Evaluated Risks and Regressions

• Risk: output-token policy could be interpreted as hiding validation evidence.
  Mitigation: the policy keeps detailed evidence mandatory in repository artifacts.

• Risk: automation terms could be misunderstood as permission to create runtime scripts.
  Mitigation: ADR-0002 and the automation contract documents explicitly preserve Markdown-only Scenario 1.

• Risk: README could become too long.
  Mitigation: the README uses bilingual sections, concise tables, and visual diagrams.

• Risk: license migration could leave conflicting license files.
  Mitigation: root LICENSE was added and FCVW/LICENSE was removed.

Validation Executed

• Confirmed the existing V0.12.0 changelog file was incomplete and should be replaced or expanded manually.
• Confirmed README includes PT-BR and EN-US sections.
• Confirmed README includes Mermaid diagrams.
• Confirmed README includes badges for framework version, release, Apache 2.0 license, and LinkedIn contact.
• Confirmed root LICENSE exists with Apache 2.0 reference.
• Confirmed FCVW/LICENSE was removed.
• Confirmed no executable automation artifacts were intentionally introduced.

Known Gaps

• The GitHub Release/tag v0.12.0 was not created through the available connector tools.
• The current repository file FCVW/changelogs/V0-12-0.md contains only a minimal placeholder and should be manually replaced with this content.
• A duplicate minimal file FCVW/changelogs/V0.12.md may require manual deletion if still present.

Suggested GitHub Release Text

Title

FrameCode VibeWork v0.12.0

Tag

v0.12.0

Target

main

Release Description

FrameCode VibeWork v0.12.0 adds Markdown-only declarative automation contracts, output-token economy guidance, a refreshed bilingual README with pipeline diagrams, and a root Apache 2.0 license.

This release preserves the framework's pure Markdown baseline while making FCVW clearer for public use, safer around automation terminology, and more economical in AI-assisted execution.

Highlights

• Markdown-only automation contracts for hooks, watchers, daemon loops, and gove...

Release V0.11.0

FrameCode VibeWork v0.11.0 (Baseline)

This release provides the clean baseline of the FrameCode VibeWork (FCVW) framework, updated to V0.11.0 and ready for use in new projects. The main repository keeps the full history, but the attached ZIP is intended to start projects from scratch while preserving only the guidelines and removing the local history.

What is new in this release:

• Continuous wiki curation: the new wiki-curator skill promotes, reviews, clusters, and tags knowledge on demand.
• Taxonomy and thematic colors: wiki/taxonomy.md defines canonical tags, themes, and theme_color for frontmatter.
• Freshness and quality metrics: wiki/metrics.md defines review cadence, source coverage, duplication, and release syntheses.
• Optimized fixed-cost mode: curation uses a single standard JIT mode, with no customizable configuration.
• Clean V0.11.0 template: baseline package regenerated with the current version and without local plan/session history.

How to use:

1. Download the FrameCode-VibeWork-Clean-Template.zip file attached to this release.
2. Extract the contents into the root directory of your new repository or project under development.
3. Consult the AGENTS.md file and the INSTANTIATION.md guide to start Phase 0 of your project.

---

Changelog V0.11.0

Version

V0.11.0

Date

2026-06-17

Release Status

published

GitHub Release Status

published

Release Type

minor

Summary

• Added governed continuous-learning support for the LLM Wiki.
• Introduced wiki-curator as a JIT skill for promotion, clustering, metadata refresh, metrics, and low-cost curation.
• Added canonical wiki taxonomy and metrics pages, including thematic frontmatter colors.
• Standardized wiki curation around one fixed optimized cost mode instead of a customizable mode.

Related Plans

• Plans/completed/P2-R2-2026-06-17-v0110-wiki-continuous-learning-governance.md

Items Created

• FCVW/skills/wiki-curator/SKILL.md
• FCVW/wiki/taxonomy.md
• FCVW/wiki/metrics.md
• FCVW/wiki/releases/v0-11-0-summary.md
• FCVW/wiki/sessions/S007-2026-06-17-v0110-wiki-continuous-learning-governance.md
• FCVW/Plans/completed/P2-R2-2026-06-17-v0110-wiki-continuous-learning-governance.md
• FCVW/changelogs/V0.11.0.md

Items Modified

• AGENTS.md
• README.md
• FCVW/README.md
• FCVW/AI.md
• FCVW/AUDIT.md
• FCVW/CONTEXT_MAP.md
• FCVW/FILESYSTEM.md
• FCVW/MANIFEST.md
• FCVW/STACK.md
• FCVW/TESTS.md
• FCVW/VERSIONING.md
• FCVW/skills/README.md
• FCVW/skills/wiki-lint/SKILL.md
• FCVW/wiki/index.md
• FCVW/wiki/log.md
• FCVW/wiki/schema.md
• FCVW/wiki/README.md

Items Removed

• None.

Justifications

• The framework needed an explicit continuous-learning loop that uses the AI model to incorporate new knowledge, revise existing content, connect related notes, keep frontmatter thematic, and measure freshness without inflating the default context.
• A fixed optimized mode better preserves the framework's token-cost pillar than exposing customizable cost modes.

Affected Files

• AGENTS.md
• README.md
• FCVW/README.md
• FCVW/AI.md
• FCVW/AUDIT.md
• FCVW/CONTEXT_MAP.md
• FCVW/FILESYSTEM.md
• FCVW/MANIFEST.md
• FCVW/STACK.md
• FCVW/TESTS.md
• FCVW/VERSIONING.md
• FCVW/changelogs/V0.11.0.md
• FCVW/Plans/completed/P2-R2-2026-06-17-v0110-wiki-continuous-learning-governance.md
• FCVW/skills/README.md
• FCVW/skills/wiki-curator/SKILL.md
• FCVW/skills/wiki-lint/SKILL.md
• FCVW/wiki/index.md
• FCVW/wiki/log.md
• FCVW/wiki/metrics.md
• FCVW/wiki/releases/v0-11-0-summary.md
• FCVW/wiki/README.md
• FCVW/wiki/schema.md
• FCVW/wiki/sessions/S007-2026-06-17-v0110-wiki-continuous-learning-governance.md
• FCVW/wiki/taxonomy.md

Functional Impact

• Adds a repeatable AI-assisted wiki curation flow for future sessions.
• Does not change application runtime behavior because FCVW remains Markdown-only.

Visual Impact

• None.

Technical Impact

• Adds a new skill and two core wiki governance pages.
• Extends wiki metadata guidance with optional thematic and supersession fields.
• Keeps curation cost bounded through JIT loading and one fixed optimized mode.

Evaluated Risks and Regressions

• Risk: skill/catalog drift. Mitigation: updated skills/README.md, CONTEXT_MAP.md, and STACK.md.
• Risk: taxonomy noise. Mitigation: canonical tag/theme page and no bulk retagging of historical pages.
• Risk: wiki-lint false positives on AICC sessions. Mitigation: aligned allowed frontmatter types with type: "session".
• Risk: version drift. Mitigation: version coherence validation across release documents.

Validation Executed

• git diff --check
• Wiki structural lint for minor release: frontmatter, index coverage, release synthesis coverage, and new page taxonomy fields checked.
• Governance validation: skill catalog consistency, version coherence, plan-state coherence, and FILESYSTEM.md coverage checked.
• Markdown fence balance and placeholder scan executed.

Known Gaps

• Historical pages were not bulk-retagged. Future wiki-curator sessions should update metadata when pages are touched for substantive reasons.

Rollback Observations

• Roll back by reverting the release commit and deleting GitHub tag/release v0.11.0 if publication must be withdrawn. No data migration, runtime artifact, or external service rollback is required.
  """

path = Path("/mnt/data/framecode-vibework-v0.11.0-release-notes-en.md")
path.write_text(content, encoding="utf-8")

print(f"Arquivo criado: {path}")
print(f"Tamanho: {path.stat().st_size} bytes")

Release V0.10.3

FrameCode VibeWork v0.10.3 (Baseline)

Este release disponibiliza o baseline limpo do framework FrameCode VibeWork (FCVW), atualizado para V0.10.3 e pronto para uso em novos projetos. O repositório principal registra todo o histórico, mas o ZIP anexado serve para iniciar projetos do zero mantendo apenas as diretrizes e removendo o histórico local.

O que há de novo neste release:

• Coerência de release e planos: status internos de planos concluídos, schema de changelog e estado de GitHub Release foram alinhados.
• Gatilhos JIT em PT-BR: skills críticas receberam gatilhos em português brasileiro para melhorar ativação sob demanda.
• Carregamento de contexto mais claro: AGENTS.md permanece como ponto de entrada primário e CONTEXT_MAP.md como primeiro mapa auxiliar.
• Arquivos grandes atualizados: README.md, AGENTS.md, MANIFEST.md e FILESYSTEM.md foram sincronizados com V0.10.3.
• Template limpo V0.10.3: pacote de baseline regenerado com a versão atual e sem histórico local de planos/sessões.

Como utilizar:

1. Faça o download do arquivo FrameCode-VibeWork-Clean-Template.zip anexado a este release.
2. Extraia o conteúdo no diretório raiz do seu novo repositório ou projeto em desenvolvimento.
3. Consulte o arquivo AGENTS.md e o guia INSTANTIATION.md para iniciar a Fase 0 do seu projeto.

---

Changelog V0.10.3

Este release consolida as mudanças publicadas no changelog V0.10.3, acumuladas em main desde o release �0.10.2.

Changelog V0.10.3

Version

V0.10.3

Date

2026-06-17

Release Status

published

GitHub Release Status

published

Release Type

patch

Summary

Governance patch to improve release validation coherence, plan-state checks, and JIT skill activation in Portuguese and English.

Related Plans

• Plans/completed/P2-R2-2026-06-17-v0103-release-governance-jit-fixes.md

Items Created

• changelogs/V0.10.3.md
• wiki/sessions/S006-2026-06-17-v0103-release-governance-jit-fixes.md

Items Modified

• ../AGENTS.md
• ../README.md
• README.md
• CONTEXT_MAP.md
• FILESYSTEM.md
• MANIFEST.md
• Plans/completed/P2-R1-2026-06-17-v0103-github-release-publication.md
• Plans/completed/P2-R3-2026-06-13-framework-agent-self-improvement-template-site.md
• Plans/completed/P3-R2-2026-06-13-v0101-cleanup-optimization.md
• Plans/completed/P3-R2-2026-06-14-final-compliance-qa.md
• STACK.md
• VERSIONING.md
• changelogs/V0.10.2.md
• skills/README.md
• skills/agent-aegis/SKILL.md
• skills/agent-hermes/SKILL.md
• skills/agent-hephaestus/SKILL.md
• skills/code-hygiene-refactor/SKILL.md
• skills/governance-validator/SKILL.md
• skills/release-checklist/SKILL.md
• skills/self-improvement/SKILL.md
• wiki/index.md
• wiki/log.md

Items Removed

• None.

Justifications

• Some completed plan files stored under Plans/completed/ still had internal status values that did not match their directory.
• The V0.10.2 changelog used a simplified format that diverged from the official release-checklist schema.
• Release checklist activation depended too much on user wording instead of version/changelog file changes.
• Several domain-agent triggers lacked Portuguese terms, reducing JIT activation reliability for PT-BR prompts.
• AGENTS.md and CONTEXT_MAP.md had ambiguous wording about which file should be read first.
• Draft PR review found that the large files listed in this changelog (README.md, AGENTS.md, FILESYSTEM.md, and MANIFEST.md) still needed to be updated in the branch diff.

Affected Files

• Governance, release, skills, and wiki Markdown files only.

Functional Impact

• No application runtime impact. This is a governance/documentation patch.

Visual Impact

• None.

Technical Impact

• Adds plan-state coherence checks.
• Adds GitHub Release Status to the release checklist changelog schema.
• Expands JIT trigger keywords in Portuguese for critical skills.
• Clarifies that AGENTS.md is the primary entrypoint and CONTEXT_MAP.md is the first auxiliary loading map.

Evaluated Risks and Regressions

Risk	Assessment
Trigger lists become too broad	Mitigated by adding narrowly scoped Portuguese equivalents only.
Changelog schema churn	Mitigated by aligning V0.10.2 and V0.10.3 with the existing release-checklist pattern.
Documentation-only version bump without GitHub release	Resolved by publishing GitHub Release v0.10.3 with release notes and clean-template asset.

Validation Executed

• Manual plan-state coherence review.
• Manual changelog schema review.
• Manual skill trigger/catalog review.
• Manual version coherence review.
• Manual large-file PR review for README.md, AGENTS.md, FCVW/MANIFEST.md, and FCVW/FILESYSTEM.md.
• git diff --check.
• Structural spot checks for version references, plan-state coherence, FILESYSTEM required entries, skill catalog consistency, and Markdown code fences.
• Manual Markdown structure review.

Known Gaps

• No programmatic Markdown linter was added, preserving ADR-0001's Markdown-only/no-script baseline.
• GitHub Release/tag publication was requested after PR #35 merge and recorded through Plans/completed/P2-R1-2026-06-17-v0103-github-release-publication.md.

Rollback Observations

Rollback: delete GitHub Release v0.10.3, delete tag v0.10.3, revert the documentation patch to V0.10.2, remove changelogs/V0.10.3.md, remove wiki/sessions/S006-2026-06-17-v0103-release-governance-jit-fixes.md, and restore prior version references.

Release V0.10.2

FrameCode VibeWork v0.10.2 (Baseline)

Este release disponibiliza o baseline "limpo" do framework FrameCode VibeWork (FCVW), atualizado para V0.10.2 e pronto para uso em novos projetos. O repositório principal registra todo o histórico, mas o ZIP anexado serve para iniciar projetos do zero mantendo apenas as diretrizes e removendo o histórico local.

O que há de novo neste release:

• Governança anti-monólito e higiene de código: novas skills, templates e gates para bloquear artefatos grandes demais, duplicação, arquivos obsoletos e limpeza sem triagem.
• Criação e melhoria controlada de skills/agentes: novos processos agent-factory e self-improvement com critérios mensuráveis.
• Template limpo Markdown-only: pacote de baseline regenerado, sem histórico local de planos/sessões/refatorações.
• QA final de conformidade: correções em wikilinks de exemplo, espelho estático de documentação e validações finais para V0.10.2.

Como utilizar:

1. Faça o download do arquivo FrameCode-VibeWork-Clean-Template.zip anexado a este release.
2. Extraia o conteúdo no diretório raiz do seu novo repositório ou projeto em desenvolvimento.
3. Consulte o arquivo AGENTS.md e o guia INSTANTIATION.md para iniciar a Fase 0 do seu projeto.

---

Changelog cumulativo V0.10.2

Este release consolida as mudanças publicadas nos changelogs V0.9.1, V0.10.0, V0.10.1 e V0.10.2, acumuladas em main desde o release �0.9.0.

Changelog V0.9.1

Version

V0.9.1

Date

2026-06-13

Release Status

published

Release Type

patch

Summary

Documentation/process patch that makes the framework actively block AI-generated monoliths and drive code hygiene/refactoring through Markdown-only skills, templates, planning gates, validation rules, and retroactive instantiation triage.

Related Plans

• P2-R3-2026-06-13-anti-monolith-code-hygiene.md

Items Created

• skills/anti-monolith-guard/SKILL.md
• skills/code-hygiene-refactor/SKILL.md
• governance/TEMPLATE_MONOLITH_GATE.md
• governance/TEMPLATE_CODE_HYGIENE_REPORT.md
• wiki/refactorings/anti-monolith-and-code-hygiene-gates.md
• wiki/sessions/S002-2026-06-13-anti-monolith-code-hygiene.md
• changelogs/V0.9.1.md

Items Modified

• ../AGENTS.md
• README.md
• AI.md
• AUDIT.md
• CONTEXT_MAP.md
• FILESYSTEM.md
• MANIFEST.md
• PLANNING.md
• README.md
• REFACTORING.md
• RETROACTIVE_INSTANTIATION.md
• STACK.md
• TESTS.md
• VERSIONING.md
• skills/README.md
• skills/agent-aegis/SKILL.md
• skills/agent-hephaestus/SKILL.md
• skills/agent-hermes/SKILL.md
• skills/orchestrator/SKILL.md
• skills/retroactive-instantiation/SKILL.md
• wiki/index.md
• wiki/log.md

Items Removed

• None.

Justifications

• Refactoring guidance existed, but agents were not forced to stop before creating mixed-responsibility modules.
• Retroactive instantiation preserved code, but did not require active hygiene triage for duplication, stale files, dead code, or monolith candidates.
• Domain agents claimed scheduler/PR/subagent behavior that may not exist in every environment. They now operate as tool-aware Markdown profiles and fall back safely when capabilities are unavailable.
• Local reference files under Referencias/ showed reusable patterns: explicit tool availability checks, concise progress discipline, memory compaction, planning before edits, validation before closure, and prompt-injection resistance.

Affected Files

• ../AGENTS.md
• README.md
• AI.md
• AUDIT.md
• CONTEXT_MAP.md
• FILESYSTEM.md
• MANIFEST.md
• PLANNING.md
• REFACTORING.md
• RETROACTIVE_INSTANTIATION.md
• STACK.md
• TESTS.md
• VERSIONING.md
• governance/TEMPLATE_CODE_HYGIENE_REPORT.md
• governance/TEMPLATE_MONOLITH_GATE.md
• skills/*/SKILL.md
• skills/README.md
• wiki/index.md
• wiki/log.md
• wiki/refactorings/anti-monolith-and-code-hygiene-gates.md
• wiki/sessions/S002-2026-06-13-anti-monolith-code-hygiene.md

Functional Impact

AI agents following FCVW now must run explicit gates before creating or expanding large artifacts and before cleanup/refactoring work involving duplication, stale files, dead code, or monolith remediation.

Visual Impact

None.

Technical Impact

• Adds two new ASE skills loaded on demand.
• Adds two reusable governance templates.
• Adds plan/audit/test closure checks for monolith prevention and code hygiene.
• Makes retroactive instantiation produce cleanup backlog without silently modifying legacy code.
• Converts domain agents into environment-aware, functional Markdown procedures.

Evaluated Risks and Regressions

Risk	Assessment
Increased governance overhead	Mitigated by CONTEXT_MAP.md and JIT skill loading; only triggered for relevant work.
Agents over-splitting code prematurely	Mitigated by size budgets as warning/block thresholds, not universal hard language rules.
Cleanup changing behavior	Mitigated by explicit behavior preservation and validation evidence.
External prompt references contaminating FCVW rules	Mitigated by AI.md reference repository safety rule.

Validation Executed

• rg --files inventory after edits.
• Skill catalog path check.
• Internal path existence check for new skills, templates, changelog, plan, and wiki records.
• Markdown-only validation; no executable test harness exists for this framework baseline.

Known Gaps

• No programmatic Markdown linter is included by design because ADR-0001 keeps the framework script-free.
• Existing historical encoding artifacts remain in older documents and were not globally normalized in this patch.

Rollback Observations

Rollback: remove the new Markdown artifacts, revert modified Markdown references to V0.9.0, and restore the previous skill catalog. No code, dependency, data, or runtime migration is involved.

---

Changelog V0.10.0

Status

published

Date

2026-06-13

Related Plan

• Plans/completed/P2-R3-2026-06-13-framework-agent-self-improvement-template-site.md

Summary

Added controlled creation and self-improvement governance for skills and agent profiles, repaired AI-usability issues in governance templates, generated a clean Markdown-only template, and refreshed the static web site to match the current framework.

Added

• skills/agent-factory/SKILL.md for measurable creation of new skills and agent profiles.
• skills/self-improvement/SKILL.md for evidence-based changes to skills and agent profiles.
• governance/TEMPLATE_AGENT_OR_SKILL_PROPOSAL.md.
• governance/TEMPLATE_SELF_IMPROVEMENT_REPORT.md.
• wiki/refactorings/agent-skill-self-improvement-governance.md.
• wiki/sessions/S003-2026-06-13-agent-self-improvement-template-site.md.
• Clean Markdown-only baseline under Template limpo/.

Changed

• Updated AGENTS.md, AI.md, PLANNING.md, AUDIT.md, TESTS.md, CONTEXT_MAP.md, STACK.md, MANIFEST.md, VERSIONING.md, README.md, FCVW/README.md, and skills/README.md.
• Updated static site files in Página web/ to describe V0.10.0, anti-monolith gates, code hygiene, agent factory, self-improvement, and clean-template distribution.
• Replaced stale visual-diff mockup links with evidence placeholders that do not imply deprecated framework-owned mockup paths.
• Reworded placeholder Markdown-link examples in skills to avoid false broken-link detections.

Validation

• Markdown fence balance scan passed.
• Skill trigger declaration scan passed.
• Skill catalog consistency scan passed.
• Key Markdown relative-link scan passed after placeholder fixes.
• Clean template contains only Markdown files and excludes development history.
• Static site references V0.10.0 and current framework features.
• In-app Browser render check was attempted but local file:// navigation was blocked by browser URL policy; validation fell back to static site data and DOM-source checks.

Residual Risks

• The framework remains Markdown-only by design; validation is declarative/manual and not a runtime test harness.
• The static site is a documentation mirror; canonical governance remains under Framework/FCVW/.
• Browser-level visual verification may require serving Página web/ through an approved local HTTP target outside the blocked file:// path.

---

Changelog V0.10.1

Status

published

Date

2026-06-14

Related Plan

• Plans/completed/P3-R2-2026-06-13-v0101-cleanup-optimization.md

Summary

Follow-up cleanup patch for V0.10.0. Removes raw HTML from Markdown README files, replaces the static site's embedded Markdown blob with a small document manifest, and sanitizes the clean template manifest to remove framework-development history leakage.

Changed

• Converted README image/support snippets from raw HTML to Markdown-native links.
• Updated framework version references to V0.10.1.
• Changed Página web/docs.html to load Markdown documents lazily from mirrored .md files instead of reading embedded full document bodies from fcvw-content.js.
• Regenerated Página web/fcvw-content.js as a compact metadata and document-manifest file.
• Regenerated Template limpo/ and replaced its manifest with a clean baseline manifest.

Validation

• Markdown fence scan passed.
• Raw HTML scan for non-template Markdown content passed.
• Skill catalog consistency scan passed.
• Relative Markdown link scan passed.
• Clean template remained Markdown-only and free of historical plan/session/refactoring artifacts.
• Static site loaded successfully through a local HTTP server.

Residual Risks

• docs.html expects the site to be served over HTTP for reliable Markdown fetching. Direct file:// rendering may be restricted by browser po...

Release V0.9.0

FrameCode VibeWork v0.9.0 (Baseline)

Este release disponibiliza o baseline "limpo" do framework FrameCode VibeWork (FCVW), atualizado e pronto para uso em novos projetos. O repositório principal registra todo o histórico, mas o ZIP anexado serve para iniciar projetos do zero mantendo apenas as diretrizes e removendo o histórico local.

Como utilizar:

1. Faça o download do arquivo FrameCode-VibeWork-Clean-Template.zip anexado a este release.
2. Extraia o conteúdo no diretório raiz do seu novo repositório ou projeto em desenvolvimento.
3. Consulte o arquivo AGENTS.md e o guia FCVW/INSTANTIATION.md para iniciar a Fase 0 do seu projeto.

---

Changelog V0.9.0

Version

V0.9.0

Date

2026-06-11

Release Status

published

Release Type

minor (by explicit user request — all changes are documentation/process, which would normally be a patch per VERSIONING.md increment criteria)

Summary

Governance gap closure release — documents four structural gaps identified during hypothesis testing: service research mandate, PR/branch/code review workflow, environment promotion workflow, and multi-agent concurrency protocol. All changes are documentation-only (pure Markdown, ADR-0001 compliant).

Related Plans

• P1-R4-2026-06-11-service-research-mandate.md
• P2-R3-2026-06-11-pr-branch-workflow.md
• P2-R3-2026-06-11-environment-promotion-workflow.md
• P2-R4-2026-06-11-multi-agent-concurrency.md

Items Created

• FCVW/changelogs/V0.9.0.md — consolidated release changelog
• FCVW/Plans/completed/P2-R3-2026-06-11-pr-branch-workflow.md
• FCVW/Plans/completed/P2-R3-2026-06-11-environment-promotion-workflow.md
• FCVW/Plans/completed/P2-R4-2026-06-11-multi-agent-concurrency.md
• FCVW/wiki/releases/v0-8-0-summary.md — consolidated session synthesis

Items Modified

GAP-1.3 — Third-Party Service Research Mandate

File	Change
AGENTS.md	Added "Third-Party Services" operational rule + Initial Checklist item referencing FCVW/AI.md §Third-Party Service Research
FCVW/AI.md	Added "Third-Party Service Research" section — mandatory research, prohibited behaviors, integration protocol, exceptions

GAP-2.2 — Pull Request, Branch Strategy, and Code Review Workflow

File	Change
AGENTS.md	Added "Code Review / Pull Requests" operational rule + dedicated section (branch naming, PR workflow, review standards by risk, cross-reference to refactoring-guide/17-branch-and-pull-request-policy.md). Added PR review item to Checklist Before Finishing a Change.
FCVW/CONTEXT_MAP.md	Added "Pull Request / Code Review" session type row

GAP-3.2 — Environment Promotion and Deployment Workflow

File	Change
FCVW/ENVIRONMENT.md	Added §5 "Environment Promotion Workflow" — environment roles table, promotion gates, rollback, single-environment fallback. Section numbering re-indexed. Frontmatter updated.
FCVW/RELEASE.md	Expanded release states to include in_staging and in_production. Added "Deployment and Environment Promotion" section — workflow, rollback, single-environment fallback.
FCVW/CONTEXT_MAP.md	Added "Deploy / Environment Promotion" session type row

GAP-5.1 — Multi-Agent Concurrency Protocol

File	Change
AGENTS.md	Added "Multi-Agent Concurrency" operational rule + dedicated section (plan-based signaling, coordination check with 3 overlap levels, agent journals, scope locking, conflict resolution, branch isolation). Added items to Initial Checklist and Checklist Before Finishing a Change.
FCVW/CONTEXT_MAP.md	Added "Multi-Agent / Collaboration" session type row

Version References

File	Change
FCVW/STACK.md	Current version updated from V0.8.0 to V0.9.0
FCVW/MANIFEST.md	Current version updated from V0.8.0 to V0.9.0. Added §14 entry for V0.9.0 release.

Items Removed

• FCVW/changelogs/unreleased/P1-R4-2026-06-11-service-research-mandate.md — consolidated into V0.9.0 (file remains on disk — pending physical deletion)
• FCVW/changelogs/unreleased/P2-R3-2026-06-11-pr-branch-workflow.md — consolidated into V0.9.0 (file remains on disk — pending physical deletion)
• FCVW/changelogs/unreleased/P2-R3-2026-06-11-environment-promotion-workflow.md — consolidated into V0.9.0 (file remains on disk — pending physical deletion)
• FCVW/changelogs/unreleased/P2-R4-2026-06-11-multi-agent-concurrency.md — consolidated into V0.9.0 (file remains on disk — pending physical deletion)

Justifications

All four gaps were identified during hypothesis testing of the framework governance layer:

1. Service research (P1-R4): Framework had no rule preventing agents from recommending services from training memory alone — risk of outdated/incompatible selections.
2. PR/branch workflow (P2-R3): Main governance entry points had no documented PR, branch, or code review process. Existing refactoring PR policy was invisible.
3. Environment promotion (P2-R3): Environments were defined conceptually but no workflow existed for promoting changes between them. Releases ended at documentation with no deployment connection.
4. Multi-agent concurrency (P2-R4): Framework assumed single-agent serialized operation — no protocol for concurrent contributors.

Affected Files

• AGENTS.md
• FCVW/AI.md
• FCVW/ENVIRONMENT.md
• FCVW/RELEASE.md
• FCVW/CONTEXT_MAP.md
• FCVW/STACK.md
• FCVW/MANIFEST.md
• FCVW/FILESYSTEM.md (verified — already up to date)
• FCVW/wiki/releases/v0-8-0-summary.md

Functional Impact

None — all changes are governance documentation only. No application code, API contracts, or persisted data were modified.

Visual Impact

None.

Technical Impact

AI agents following the framework will now:

• Research third-party services via Gravity Index before recommending (instead of relying on training memory)
• Follow a defined branch naming convention and PR workflow for all changes
• Execute releases with environment promotion gates and rollback procedures
• Coordinate with other agents via plan-based signaling in Plans/in_progress/

Evaluated Risks and Regressions

Risk	Assessment
New rules increase governance overhead	Mitigated by CONTEXT_MAP.md selective loading — agents load only relevant rules per session type
Contradiction with existing PLANNING.md risk gates	Reviewed — all new rules are additive, not contradictory
CI/CD reference in PR rules	Corrected to "automated tests or validations" — aligned with ADR-0001 (CI/CD out of scope)
Stale plan files in pending/ and in_progress/	Marked as superseded — authoritative versions in completed/

Validation Executed

• Code review: 4 plans reviewed in 12 total review rounds (3 per plan), all issues resolved
• Cross-reference verification: AGENTS.md → AI.md, AGENTS.md → refactoring-guide, ENVIRONMENT.md ↔ RELEASE.md
• Plan consolidation audit: 15 plan files mapped, 7 stale copies identified and marked
• MANIFEST.md §14: 4 new entries verified

Known Gaps

• Stale files in FCVW/Plans/pending/ and FCVW/Plans/in_progress/ remain on disk (marked superseded — pending physical deletion)
• Changelog fragments in unreleased/ remain on disk (consolidated into this changelog — pending physical deletion)

Rollback Observations

Rollback: revert all markdown edits and restore STACK.md and MANIFEST.md version to V0.8.0. No data migration required.

v0.7.5

FrameCode VibeWork v0.7.5 (Baseline)

Este release disponibiliza o baseline "limpo" do framework FrameCode VibeWork (FCVW), pronto para uso em novos projetos.

O que há de novo neste release:

O repositório principal do framework registra o histórico detalhado e os planos de alteração de seu próprio desenvolvimento. Para facilitar o início de novos projetos, este release disponibiliza o pacote FrameCode-VibeWork-Clean-Template.zip, que limpa esses registros locais mantendo a estrutura original:

• Estrutura de Pastas Preservada: Diretórios operacionais vazios para Plans/, changelogs/, wiki/sessions/ e audits/.
• Diretrizes e Regras do Framework: Arquivos oficiais de baseline (AGENTS.md, README.md, MANIFEST.md, PLANNING.md, STACK.md, TESTS.md, etc.).
• Gabaritos de Governança (Templates): Arquivos de modelos vazios em FCVW/governance/ e FCVW/wiki/templates/ prontos para serem preenchidos.
• Skills JIT: Habilidades sob demanda para agentes de IA localizadas em FCVW/skills/.
• Manual de Refatoração: Guia operacional completo de refatoração governada em FCVW/refactoring-guide/.

Como utilizar:

1. Faça o download do arquivo FrameCode-VibeWork-Clean-Template.zip anexado a este release.
2. Extraia o conteúdo no diretório raiz do seu novo repositório ou projeto em desenvolvimento.
3. Consulte o arquivo AGENTS.md e o guia FCVW/INSTANTIATION.md para iniciar a Fase 0 do seu projeto.