Publication note / updated 28 September 2026

About the Pre-Launch Desk

The narrow editorial idea

ProgtiProj is designed as an English-language UK editorial notebook about completing small software projects. Its subject is the gap between “I have an idea” and “another person can use and maintain the first release”. The current issue concentrates on six connected decisions: outcome, scope boundary, data shape, state transitions, failure handling and verification.

The publication is deliberately generic about technology. It does not name programming languages, frameworks, hosting companies, repository services or package systems. That choice keeps attention on decisions that transfer between stacks. It also prevents the articles from pretending that one named product settles questions of state, ownership or failure.

What the desk would publish

A real ProgtiProj desk would commission compact, worked notes. Every article would need a visible author, date, checkable assumptions, an original table or calculation, and a section explaining when the method does not apply. Runnable examples would need technical review in a clean environment. Pseudocode would be labelled. Claims based on measurement would identify the method and scope, not masquerade as universal fact.

The current six articles are pre-launch editorial demonstrations. Their author names and roles are illustrative labels, not verified people or credentials. They do not report classroom teaching, client work, production incidents or empirical testing. Read the author-role disclosures and proposed standards for the intended accountability model.

What this is not

ProgtiProj is not a school, training provider, code repository, recruitment service or commercial course. It has no students, enrolment, certificates, active subscriptions or promised outcomes. It does not distribute executables, starter archives or source bundles. It makes no job or salary claims, and it does not rank or recommend products.

Educational examples cannot validate a real system. Security-critical, safety-critical, medical, financial, regulated, real-time and high-scale projects require specialist methods and independent review. Accessibility, privacy, security and legal duties need context-specific work too. A six-pass notebook can reveal questions; it cannot sign them off.

Accountability still required

Before publication, a responsible operator must provide their legal identity and contact details, appoint real accountable editors, choose and disclose a funding or commercial policy, and put a working mailbox behind the visible address. The operator must arrange UK legal and privacy review, technical fact and code review, image licensing checks, accessibility and mobile testing, and corrections ownership.

Until then, the banner remains prominent, the form remains a no-send preview and editor@progtiproj.com remains visibly described as unverified and unmonitored. That is less convenient than invented certainty. It is also honest.