1 bed flat for sale

Arena Tower, 25 Crossharbour Plaza, London E14

Aria consolidation - phase 2A

Complete Preservation & Integration Readiness

You are continuing the aria consolidation project following the completed Phase 1 audit.

Role: Principal Software Architect, Release Engineer and Technical Lead.

Execution: Claude Opus 5.5 - High Thinking.

Objective

Prepare aria for integration into one canonical development line without losing existing functionality, private data, approved designs or historical evidence.

This phase is authorized to perform non-destructive preservation and verification operations.

It is not authorized to merge branches, deploy code, restart production services, delete worktrees or modify production data.

1. Read the completed consolidation reports

Read all documents in:

Docs/consolidation/ARIA_CONSOLIDATION_20261017/

Treat the executive report, preservation manifest, integration strategy and execution plan as the primary references.

Also read .

Verify that current repository states still match the recorded hashes.

2. Complete preservation

The previous phase preserved 575 files and inventoried 1,767 exclusions.

Review every excluded entry by category.

Classify each as:

* Irreplaceable source or design work.
* Private runtime data.
* Configuration or credentials.
* Unique evaluation evidence.
* Historical documentation.
* Reproducible build artifact.
* Dependency cache.
* Duplicate.

Identify which exclusions require preservation before integration.

Do not print or expose private content.

Do not place credentials, personal databases or private records in Git.

Create additional local snapshots where safe and necessary, using new destinations and verified sha-256 hashes.

For sensitive or irreplaceable material, prepare an encrypted off-device backup plan. Do not transfer private data to an external destination without explicit owner approval.

If an item cannot be safely classified, preserve it in place and flag it for review.

3. Verify recovery readiness

Confirm that all critical source and design states are recoverable.

Verify:

* Approved Liquid Glass files.
* Model Management commits.
* Cognitive Engine commits.
* Legacy Gemini embeddings implementation.
* Living design assets.
* Unique benchmark evidence.
* Git history and refs.
* Existing worker configuration dependencies.

Distinguish source preservation from operational database recovery.

Do not claim production recovery is proven until an isolated restore has succeeded.

4. Prepare exact commit scopes

For every dirty worktree that contains changes needed for integration, produce an explicit file list.

For each file indicate:

* Absolute source path.
* Relative repository path.
* sha-256.
* Git status.
* Whether it contains private information.
* Whether it is already committed elsewhere.
* Whether it is required for the consolidated product.
* Proposed destination.
* Proposed integration method.

Do not commit dirty work automatically.

Present the exact proposed commit scopes for owner approval.

5. Verify integration readiness

Confirm the proposed strategy:

* Cognitive Engine cea8719 as integration baseline.
* Existing Git history retained.
* aria-living as eventual canonical development location.
* Isolated integration worktree.
* Model Management integrated additively.
* Current Web Glass preserved.
* Approved iOS Liquid Glass reconciled with cognitive streaming.
* Production 3ddae54 unchanged.

Identify any newly discovered conflict or dependency that would invalidate this approach.

6. Prepare Phase 2B

Produce an implementation-ready plan for the integration worktree.

Include:

* Proposed branch name.
* Proposed worktree location.
* Exact baseline sha.
* Required preservation checkpoints.
* Integration order.
* Expected conflicts.
* Test commands.
* Acceptance criteria.
* Rollback procedure.
* Operations requiring separate approval.

Do not create the integration branch or worktree yet.

7. Output

Create:

Docs/consolidation/ARIA_CONSOLIDATION_20261017/PHASE2A/

Generate:

1. PRESERVATION_COMPLETION.md
2. EXCLUDED_FILES_DISPOSITION.md
3. DIRTY_WORKTREE_COMMIT_SCOPES.md
4. RECOVERY_READINESS.md
5. INTEGRATION_READINESS.md
6. PHASE2B_EXECUTION_PLAN.md
7. PHASE2A_EXECUTIVE.md

8. Stop condition

Stop after completing preservation, verification and documentation.

Do not merge, deploy, restart services, delete files, change Git history or modify the production environment.

Report:

* Preservation completeness.
* Remaining irreplaceable items.
* Backup and recovery status.
* Exact dirty-file scopes awaiting approval.
* Integration readiness.
* Critical blockers.
* Recommended next operation.

The objective is to enter Phase 2B with zero unaccounted-for source or design work and a clearly reversible integration plan.