T
texed.co.uk Code Documentation www.texed.co.uk ยท 1.0.0-initial-record

Monthly code record.

This page is the initial code documentation record for texed.co.uk. It gives the refined file system a stable public record for what exists, why each file exists, and how future monthly code summaries can be added without a database.

Records3
Visible2
ModeHTTPS

Find a record

Initial texed.co.uk code record

texed.co.uk-2026-07-initial-code-record 2026-07 active monthly_code_summary

texed.co.uk is being organised as a file-first PHP code system with a robust public index, private administrator file management, hardened login and logout boundaries, and JSON-driven navigation records.

Record identity

Sitetexed.co.uk
Created2026-07-06
Updated2026-07-06
Tagstexed, code, documentation, php, json, vps, monthly-docs

Environment

hostingBluehost Enhanced VPS - NVMe 8
server modelself-managed Ubuntu VPS with direct console access
runtimePHP files under the public site root
data modelplain files, JSON records, and optional private runtime storage
visual systemblack, white, and faded purple only
PathRoleStateNote
index.php public navigation surface refined Reads buttons.txt, menu.json, and tools.json, then displays public tools safely.
admin.php private file-system control panel refined Restricts actions to the detected site root and creates backups before destructive file operations.
login.php private session entry boundary refined Uses CSRF validation, rate limiting, private logs, secure cookies where HTTPS is available, and optional two-factor challenge flow.
logout.php private session exit boundary refined Destroys the server-side session, expires the session cookie, and logs the closure reason.
buttons.txt plain-text navigation record active Contains the Code Documentation link to documentation/code.php.
menu.json JSON public menu record active Contains the Code Summary menu item.
tools.json JSON public tools record active Contains the Code Summary tool item.
documentation/code.php monthly code documentation viewer created Displays this initial record and can merge future records from code.records.json.

Changes

  • Established an initial code documentation page for the texed.co.uk file-first site model.
  • Recorded the core files that form the public navigation, private administration, login, and logout system.
  • Aligned the public documentation page with the same self-contained styling and no-CDN constraint used by the refined fil

Next actions

  • Deploy documentation/code.php into the public documentation directory.
  • Keep buttons.txt, menu.json, and tools.json pointing to documentation/code.php.
  • Add future monthly records in code.records.json when the codebase changes.
  • Use the admin panel to create backups before editing production files.

BertoTools platform code record

bertotools-platform-2026-07-code-record 2026-07 active platform_code_summary

BertoTools is being modelled as a file-first platform for documenting inputs, process events, outputs, and executable resolutions through JSON records and PHP display surfaces. The platform direction is a physical data warehouse joined to a tautological pointer-and-resolve database system, so client-facing resolutions can be produced while each input, process step, and output remains traceable.

Record identity

Sitetexed.co.uk
Created2026-07-06
Updated2026-07-06
Tagsbertotools, platform, json, records, php, vps, data-warehouse, pointer-resolution

Environment

hostingBluehost Enhanced VPS - NVMe 8
server modelself-managed Ubuntu VPS with direct console access
runtimePHP pages under the public site root with optional private runtime storage
data modelJSON-first event records for inputs, process events, outputs, and executable resolutions
interface modelpublic documentation surfaces plus private admin file-system control
PathRoleStateNote
documentation/code.php monthly code documentation viewer active Loads code.records.json and merges platform records into the visible code summary.
documentation/code.records.json platform record source created Stores the BertoTools platform entry and other future code records without requiring a database.
admin.php private file-system administration boundary refined Supports controlled editing, upload, backup, and deletion operations inside the site root.
index.php public navigation and launch surface refined Presents JSON and text-file driven navigation for public visitors.
buttons.txt, menu.json, tools.json public navigation records active Expose documentation/code.php as the Code Summary entry in plain-text and JSON formats.

Changes

  • Created the first external code record describing the BertoTools platform direction.
  • Defined BertoTools as a JSON-first platform layer for traceable input, process, output, and executable-resolution record
  • Connected the BertoTools record to the refined texed.co.uk PHP file-system and public documentation model.

Next actions

  • Create a BertoTools-specific JSON schema for input_record, process_event, output_artifact, pointer, and executable_resol
  • Add a public documentation page for the BertoTools platform once its first executable resolution workflow is ready.
  • Keep each monthly BertoTools update in code.records.json so the platform history remains append-only and reviewable.
  • Use admin.php to edit production records only after taking backups or using the built-in backup-before-save flow.

Future record format

To add future records, create documentation/code.records.json beside this file. Use a top-level records array. Each record may contain id, period, title, summary, environment, components, changes, next_actions, and tags.