You are here: Knowledge Archive
A structured home for sources, readings, claims and the context that makes them reusable.
Example: Save a research paper with your note about why it matters to a current project.
Institutional memory for Arkan5 and Atlas5. What we decided, when we decided it, and why.
Read-only in the app. The archive itself lives as plain markdown in docs/knowledge-archive/.
Export opens your browser's print dialogue — choose “Save as PDF”. Nothing leaves this browser.
Searches all 62 archive documents: foundation; heart, mind and frontier; Atlas5; ARCHI5; ideas and frontier; decision history; and every session log.
Exported 2026-11-13 from the Atlas5 private preview. Browser-local export; nothing left this device.
Decision: Generated district artwork driven by record density and recency, with an optional browser-local personal cover image
Why: The icons had fallen behind the rest of the interface. A photo gallery would have cost navigability; signal-driven artwork keeps every visual change meaningful.
Superseded: Flat district silhouette icons on Map5
Source: docs/knowledge-archive/decision-history.md
Decision: Readable inside Atlas5 at /knowledge: search, decision timeline, send-to-Capture, PDF export
Why: Memory that is only stored is not memory in use. The archive itself remains plain markdown; the application only reads it.
Superseded: Knowledge Archive readable only as files in the repository
Source: docs/knowledge-archive/decision-history.md
Decision: Arabic as a first-class interface mode: EN / العربية control, RTL layout, Arabic typography, translated navigation and disclosures
Why: Arabic is part of the launch direction. Untranslated strings fall back to English rather than to machine translation, so the translation state stays honest.
Superseded: English-only interface, Arabic listed as a future capability
Source: docs/knowledge-archive/decision-history.md
Decision: Three-level district imagery: personal image, then user-approved contextual image, then a designed architectural photograph per district; density and recency now govern selection, cropping, intensity and drift rather than drawing
Why: Drawn massing reads as illustration. Moving the intelligence from drawing to selection keeps every change meaningful while raising the visual register to something credible for architects and researchers.
Superseded: Generated skyline artwork drawn from density and recency
Source: docs/knowledge-archive/decision-history.md
Decision: Arabic completed for the settled bodies of Home, Map5 and Capture, including empty states, disclosures, buttons and helper text
Why: Arabic is a launch language; a translated shell over English bodies is the second-class experience the earlier decision existed to avoid.
Superseded: Arabic covered shell and navigation only
Source: docs/knowledge-archive/decision-history.md
Decision: AI image understanding classified HIGH RISK and not implemented — imagery enters Map5 only when assigned or approved by the person
Why: Automatic reading of photographs would break the metadata-only promise; it is documented rather than silently introduced.
Superseded: (new)
Source: docs/knowledge-archive/decision-history.md
Decision: User-defined districts: rename, describe, recolour, re-icon, re-image, reorder, add, hide and restore, with starting templates and a Start-from-scratch option
Why: Atlas5 serves different lives, professions and cultures; academic terminology must not constrain a general user. A district's internal identity stays permanent so renaming never detaches a Rukon, record or history entry, and earlier names are preserved. The original structure survives as the Academic template.
Superseded: Map5 districts fixed for every user (Home & Family, Work & Practice, Studies, Teaching, Research, Art, Property)
Source: docs/knowledge-archive/decision-history.md
Decision: Adaptive districts read system-wide, including Plan, Archive, Organise, Portfolio and detail pages; Organise routes by district instead of fixed domain; search matches previous district names
Why: A structure the person owns must be honoured everywhere, or the interface misstates where their records live. Internal identity and name history stay permanent.
Superseded: Districts configurable but read only by Map5 and Home
Source: docs/knowledge-archive/decision-history.md
Decision: Arabic parity across all remaining routes (Plan, Library, Disk, Settings, Desk, Archive, Review, Inbox, Organise, Portfolio, Rukon detail, Life Station detail), with area-owned string modules and dir="auto" on user content
Why: A translated shell over English bodies is the second-class experience the earlier Arabic decision existed to avoid. Generated rule sentences remain English and are recorded as deferred rather than fake-translated.
Superseded: Arabic covering shell, Home, Map5 and Capture
Source: docs/knowledge-archive/decision-history.md
Decision: "File name and approximate size only"
Why: The earlier wording overstated the logic. Accuracy of user-facing claims outranks reassurance.
Superseded: Duplicate detection described as matching "file name, size and date"
Source: docs/knowledge-archive/decision-history.md
Decision: Suggestions described as rule-based
Why: The logic is keyword, year and file-type matching. Calling it AI would be a claim the system cannot support.
Superseded: Suggestions described as AI
Source: docs/knowledge-archive/decision-history.md
Decision: Domain named "Practice & Company"
Why: Clearer to practising architects and to firms; distinguishes personal practice from company record.
Superseded: Domain named "Professional Work"
Source: docs/knowledge-archive/decision-history.md
Decision: "Map5"
Why: Family resemblance with Arkan5 / ARCHI5 / Atlas5 naming; the map is the product's centre, not a personal folder.
Superseded: Navigation item "My Map"
Source: docs/knowledge-archive/decision-history.md
Decision: "Create a Rukon"
Why: An instruction reads more clearly than a noun; reduces ambiguity for first-time users.
Superseded: "New Rukon" button
Source: docs/knowledge-archive/decision-history.md
Decision: Personal city map with districts, tabs, carousels, mobile bottom navigation
Why: The first build was legible but text-heavy and did not feel like a place. The earlier layout is retained as the source of the information architecture.
Superseded: Report-style stacked screens
Source: docs/knowledge-archive/decision-history.md
Decision: Five-item primary navigation (Home, Map5, Capture, Plan, Library), with the rest indexed under Library
Why: Rule of Five; the eight-item menu forced choice before orientation. The eight areas all still exist.
Superseded: Eight-item primary navigation (Home, My Map, Inbox, Archive, Portfolio, Organise, Review, My Desk)
Source: docs/knowledge-archive/decision-history.md
Decision: User-confirmed metadata links ("Mark as a version of…")
Why: Atlas5 never reads file contents, so it cannot compare them. The relationship is asserted by the person and recorded as such.
Superseded: Version relationships implied comparison of files
Source: docs/knowledge-archive/decision-history.md
Decision: Frozen private preview
Why: Founder instruction: ARCHI5 evaluator findings take precedence over all new development and expansion.
Superseded: Continued feature development
Source: docs/knowledge-archive/decision-history.md
Decision: Stopped, concentrating exclusively on outstanding evaluator findings, beginning with Package 1: Access Control and Privacy
Why: Founder instruction (Dr. Raed Qaqish). Evidence of closure precedes new capability.
Superseded: Ongoing development and expansion
Source: docs/knowledge-archive/decision-history.md
Decision: Included with Arkan5 at launch, no separate charge for Arkan5 users
Why: Nonprofit orientation: access before revenue.
Superseded: Atlas5 as a separately charged product
Source: docs/knowledge-archive/decision-history.md
