Download the PHP package karim-ashraf/lara-architect-ui without Composer
On this page you can find all versions of the php package karim-ashraf/lara-architect-ui. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download karim-ashraf/lara-architect-ui
More information about karim-ashraf/lara-architect-ui
Files in karim-ashraf/lara-architect-ui
Package lara-architect-ui
Short Description Developer workspace for understanding Laravel architecture through Lara Architect memory.
License MIT
Homepage https://github.com/gubakareem/lara-architect-ui
Informations about the package lara-architect-ui
Lara Architect UI
Architecture Companion — a developer operating system for Laravel architecture, beside the IDE.
Prerequisite (required)
You must install the core package first:
lara-architect-ui only works with karim-ashraf/lara-architect ^1.5.
Without core there is no architecture memory, no snapshots, and nothing for the Companion to show.
Product brand: Lara Architect — Architecture Memory and Improvement Platform for Laravel
Composer: karim-ashraf/lara-architect-ui
What this package is
lara-architect-ui does not analyze code.
It is the Architecture Companion: each screen answers one question.
| Nav | Question |
|---|---|
| Home | What should I do now? |
| Issues | What is wrong, where, and why? |
| Actions | What can Lara Architect do for me? |
| Knowledge | What does the system remember / believe? |
| History | What happened over time? |
| Settings | How is the Companion configured? |
Dependency direction is one-way: UI → core. Core must never depend on UI.
| Owns | Does not own |
|---|---|
| Rendering · interaction · developer experience | Analyzer · memory truth · events · contracts |
Milestone (0.2): Open Architect → Home answers “what next?” in under 10 seconds.
Product direction: ADR-0009
Open the Companion
Legacy /architect/workspace redirects to Home.
Acceptance (Phase 1)
- [x] Open context (
/architect/workspace?context=ProductController) - [x] See health
- [x] See issues
- [x] Understand why (select issue → explanation)
- [x] See possible action
- [x] Copy context
- [x] Preview Fix — decision screen consuming
FixProposalonly (Apply later)
Requirements
| Requirement | Detail |
|---|---|
| Core (required first) | karim-ashraf/lara-architect ^1.5 — install before this package |
| PHP | ^8.2 |
| Laravel | 11 / 12 / 13 |
| Node.js | 18+ with npm (build Workspace assets once) |
Install
1. Core first
2. Then Workspace UI
Until Packagist lists this package, add a VCS repository in your app composer.json:
3. Build and publish assets
Local path develop (optional)
Both packages as siblings:
Update
If update fails with would clobber existing tag:
Open:
JSON (same snapshot adapters use):
Architecture
Domain language only: WorkspaceShell, IssueList, IssueDetails, ActionPanel, FixPreviewShell — not Dashboard / Widget.
Phase 2 Preview: React never generates code. Metric = Proposal Understanding Rate (what / why / risk / verification in ~30s).
Dev
With npm run dev, the Blade view loads the Vite client when assets are unpublished.
Phase 1.5
Workspace Intelligence — breadcrumb, priority issues, impact dimensions, related context, neighborhood map.
Phase 2 — Fix Preview
Decision screen (not a diff editor):
Returns FixProposal JSON (summary, change_set, architecture_impact, status: viewed).
Phase 2.1 — Change Understanding ✅
Milestone: know what changes, where, and how architecture improves — before mutation.
Phase 3 — Controlled Change ✅
Not “Apply Fix”. Architectural event:
- Safe proposals: Start Improvement
- Assisted/Design: Apply Later records
ProposalReviewedonly (no mutation) - Session recorded only after verification passes (
storage/architect/sessions/) ChangeExecution.eventsis append-only (Replay-ready)
Phase 3.1 — Improvement Confidence ✅
After Session: “Did this improvement help?” → Yes / Not really.
Feeds Improvement Success Rate (storage/architect/metrics/improvement_success.json).
Phase 4 — Architecture Memory ✅
History panel: recent improvements + chronological Replay. Event stream under storage/architect/events/. Baseline under storage/architect/baseline.json.
Phase 4.1 — Architecture Story ✅
History explains itself: Problem → Decision → Change → Proof → Result (+ period trend). Events carry correlation IDs for Replay chains.
Still postponed: AI · VS Code · GitHub · dashboards.
All versions of lara-architect-ui with dependencies
illuminate/support Version ^11.0|^12.0|^13.0
illuminate/http Version ^11.0|^12.0|^13.0
illuminate/routing Version ^11.0|^12.0|^13.0
illuminate/view Version ^11.0|^12.0|^13.0
karim-ashraf/lara-architect Version ^1.5