personal-management-system
Your web application for managing personal data.
Runssource: GitHubhomepagePHPMITcommit c138c6db98b1
PHP, MIT licensed. The project labels itself: content management, crm, dashboard, dashboards, docker, finance management, free and manager.
personal-management-system runs. An Argusic agent installed it in 18 minutes and hit 9 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Symfony 5.4 app running with PHP 8.3.0, MariaDB 10.11 backend, 44 database tables, user [email protected] in DB, login endpoint returns JWT token
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 97.3 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- MariaDB not installed, no Docker available6 minutes
- PHP not available in the container2 minutes
- MariaDB client missing libncurses.so.62 minutes
- composer.lock packages require PHP ^7.x (various dev packages) and ext-sodium1 minute
- symfony/twig-bundle was not installed despite being in bundles.php1 minute
- Doctrine cache configured for APCu which is not available1 minute
- Install time
- 18 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 9 hit, 9 fixed with no human help
- How the result was proved
- curl http://127.0.0.1:8082/login (POST with username/password) returned HTTP 200 with JWT token; GET /can-register returned 200; Symfony console commands (cache:clear, doctrine:schema:create, doctrine:fixtures:load --append) all succeeded
- Model tokens used
- 434,160
- Exact commit tested
- c138c6db98b1
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
# Check php server log cat /tmp/php-server.log 2>&1 | head -5 || echo "no log"' in /work/repo succeeded in 0ms: 1 1 [Fri Sep 25 01:57:37 2026] PHP 8.3.0 Development Server (http://127.0.0.1:8082) started [Fri Sep 25 01:57:40 2026] 127.0.0.1:59432 Accepted [Fri Sep 25 01:57:40 2026] 127.0.0.1:59432 [200]: GET /login [Fri Sep 25 01:57:40 2026] 127.0.0.1:59432 Closing [Fri Sep 25 01:57:48 2026] 127.0.0.1:42046 Accepted tokens used 434,160
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 18 minutes.
- Recovered from all 9 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
content-managementcrmdashboarddashboardsdockerfinance-managementfreemanagermitnote-takingopen-sourcepassword-managerpersonal-financepersonal-managementphpprivacyproductivityself-hostedsymfonytodo-list
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/personal-management-system)Questions
- Does personal-management-system run?
- Yes. personal-management-system runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 9 errors on the way, and recorded the session.
- How did Argusic test personal-management-system?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit c138c6db98b1. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test personal-management-system?
- The run that produced this verdict cost $0.16: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does personal-management-system take to install?
- 18 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does personal-management-system need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing personal-management-system?
- 9 things broke in the recorded run, and 9 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for personal-management-system?
- All 3 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.