mmcats-legacy — README.md
Professional experience
- Document type
- Public repository documentation snapshot
- Purpose
- Supports bounded professional information and project references.
- Stable document identifier
repository-mmcats-legacy-readme-md- Source origin
- Allowlisted public documentation pinned to a verified public commit. Reported tests, performance and deployment statements have not been independently reproduced by this corpus.
- Repository source file
content/portfolio/published-synchronization.json- Authorship
- Unknown — human or AI authorship has not been established.
- Review / publication
- Publication approval recorded.
- Publication terms
- Public display requires record-level publication approval; original source copyright and license remain applicable.
- Review date
- 2026-10-29T05:02:45.301Z
- Canonical English content revision
- Not established by a source history.
- Repository source commit
5c9ca20352d80d475dd558c20a896b24522e1ef0- Repository commit date (not a document editorial date)
- Source content fingerprint
ece73e3f3a8644eff4d0d5d4da0338e7df25635ac8d61a01216db5e2837728db- Ingestion observation
source-2a0425b5080d449f
Document content
Reviewed public source snapshot.
mmcats-legacy: public repository documentation snapshot. Statements below are repository-reported, not independently reproduced test, performance, production or business outcomes. # MMCATS — Legacy Asset Management System
Originally developed around 2015 as a college/diploma final project (owner-provided context), MMCATS is an asset register from an earlier stage of the owner's engineering development. It manages organizational assets, companies, divisions, staff, users and related attachments.
**Unmaintained historical software — not production-ready.** Known security and correctness limitations remain. No successful application boot, test-suite execution or business workflow has been verified in this assessment. Do not deploy it publicly or use it with real personal information.
## Original technology and architecture
The source establishes Ruby on Rails 4.1.8, Devise 3.4.1, SQLite configuration, ERB, the historical Rails asset pipeline and Bootstrap/jQuery-era frontend references. This archive does not independently verify a MySQL, Azure or Nginx deployment.
Six database entities form a Rails monolith: assets hold register/financial/lifecycle fields; companies and divisions represent organizations; staffs represent people referenced by assets; uploads store binary attachment content; users hold Devise authentication data. Source workflows cover CRUD, name search, sorting, five-row pagination, disposal/restore and attachment upload/download. These are static source observations, not successful runtime demonstrations.
## Snapshot integrity and omissions
## Explore the source and evidence
- [Application source](app/), [configuration](config/), [schema/migrations](db/) and [historical tests](test/). - [Architecture](docs/legacy/ARCHITECTURE.md) and [data/workflows](docs/legacy/DATA_AND_WORKFLOWS.md). - [Risk register](docs/legacy/RISKS.md): VERIFIED-STATIC facts and DEFECT-CANDIDATE hypotheses are distinct; no real-world exploit is claim
Content hash: b2e80c36597a13a65f8a3ad9edd0d3116c2eca91ac6aa192de2467742544a968