Make a profile to remember, then make the work useful

We are building TXTWRK so digital profiles become living records. A profile should be more than a static biography and more than a stream of short posts. It should be a working base where a person, page, organisation, business or community can show what they are doing, what they need, what they offer and what they have contributed.

We began publicly as a brand on January 12, 2024. Since then, the platform direction has grown into a combined system for public work, local insight, media, feedback, education, commerce, AI-assisted creation, API-connected websites and long-term digital memory.

The mission is practical: help people make text work in real life. That means turning posts into evidence, checklists into work containers, feedback into local signal, addresses into real-world discovery and profiles into useful public identity hubs.

Profiles, pages and profile intelligence

Profiles are the base layer of TXTWRK. A profile can represent a person, brand, page, community, local place, business, movement, official account, project or organisation.

A TXTWRK profile can carry identity, images, covers, labels, followers, opening times, applications, grouped feedback, questionnaires, business opportunities, addresses, posts, products, donations, investment routes and public work records.

Profile intelligence turns the profile into structured data. We can support areas such as professional profile, industry, products and services, community involvement, career goals, skills, lifestyle preferences, mentorship interests, availability and visibility settings.

Official pages can also move toward approved contributor access, where a page can accept journalist-style contributors without handing over the main account.

The universal composer

Posts are the main publishing unit across TXTWRK. A post can be text, media, an event, a checklist, feedback, a question, a product, a donation request, an investment item, a covered post, paid content, location content, story mode, 3D content or work evidence.

The post box is becoming a universal composer. It should help users write, attach media, classify content, understand data usage, use AI support, choose where a post can surface and protect records where money or commitments are involved.

Post filtering can support areas such as upcoming, mentions, features, loved, favourited, acknowledged, humour, reflections, drawn, audio, photos, videos, activity, links, MP3, CSV, story mode, 3D content, web impressions, investment, checklists, feedback, pledges, donations, products, questions and community content.

Photos, video, audio, MP3, story mode, 3D and web impressions

Media on TXTWRK is not only decoration. It supports evidence, storytelling, education, products, local reporting, work records and personal expression.

Media Reels extends this further by letting media posts surface through a focused discovery path, where the user can decide whether their media is allowed to appear.

Public work containers

Checklists are one of our strongest systems because they turn work into visible structure. A checklist can include groups, items, applications, comments, replies, uploads, threadlets, hidden states, topic updates and worker visibility.

We use checklists for development, education, volunteering, campaigns, business tasks, open-source work, student experience, public participation and project planning. They are not just task lists; they are public work containers.

Checklisting is the behaviour around the checklist: applying, commenting, uploading evidence, replying, acknowledging, opening topic updates, creating threadlets and building a record of contribution.

Feedback, questions, questionnaires and public proof

Feedback lets people express views around streets, services, organisations, places, posts, public matters and community issues. It can connect to locations, organisations, names and profile records so it becomes organised insight rather than isolated comments.

The street feedback direction is central: people should be able to have a say on how their street looks, works and plays. Feedback becomes a public signal when tied to place, profile and time.

Questions and questionnaires bring structure to public input. A post can ask a question; a profile or page can publish questionnaire sets; visitors can answer where they have not already submitted a response.

Textbook local proofs build on this idea by showing what is in the air today: issues, amenities, access, sentiment, emergency signals, mental-health signals and local service evidence.

Maps, addresses, timetables and local discovery

TXTWRK is designed to work globally while still making local discovery useful. Location hierarchy can support continent, sovereign state, country, region, district, locality and place.

Addresses allow profiles and organisations to expose shops, headquarters, service points, public places and timetable-linked opening information. Timetables show opening times, activities, schedules, shop availability, events and business periods.

When addresses and timetables connect, users can discover what is open, where it is and what type of place it is. This also supports maps, local posts, feedback, events and API widgets.

All Activity, discovery, mentions and notifications

All Activity is the live pulse layer. It lets people see more than posts: profile changes, info reels, feedback, checklists, events, products, workspaces, API access, mentions and monetisation activity.

The activity system can include global/local scope, username search, year, month, order and activity type filters. This helps users pan through what is happening across the network without manually checking every profile.

Notifications make the system practical. Users need to know when someone comments, replies, mentions them, applies, acknowledges, pledges, attends, gifts, donates, purchases or engages.

Mentions can happen across posts, comments, subthreads, notes, features and Info Reel records such as Notes, Needs, Contributions, Timetable, Intel, To Dos, Financials, Quarterlys and Shares.

Business management, opportunities and work records

TXTWRK is work-ready. Business Management connects applications, opportunities, profile data, addresses, timetables, financials, quarterly records, shares and public business information.

Business Opportunities are being extended with profile visibility controls, so users can choose whether an opportunity is featured on their profile separately from the create/edit form.

Notes, Needs and Contributions show the state of work. Notes record ideas or updates. Needs show what someone requires and when. Contributions record how someone helped a profile, channel, project or organisation.

Intel, To Dos, Financials, Quarterlys and Shares extend this into deeper records: what is known, what needs doing, what happened financially, what changed quarterly and what ownership or share-style records exist.

Products, donations, pledges, investment, paid content and coins

TXTWRK includes value routes because public work often needs support. Products, donations, pledges, investment, paid content, covered content, coins, gifts, advertising and subscriptions all sit in this area.

Products allow people and organisations to list items for sale through posts and profile displays. The planned product layer can show featured products globally, nationally, locally or on a profile with search/filter support.

Donations support posts and profiles. Investment routes allow opportunity and funding direction to sit beside the public story and evidence of the work. Pledges let users signal commitment around posts, causes and community actions.

Protected posts matter where money or commitment has happened. If a post has secured investment, donations, product purchases or other value-linked actions, preservation rules help keep public context intact.

Website widgets, external domains and TXTWRK infrastructure

API kits are one of the most important future-facing TXTWRK layers. They turn TXTWRK from only a website into infrastructure that external sites and domains can use.

ChatGPT, Copilot, Grok, Gemini, AID and working with AI

Working with AI is now part of the TXTWRK story. We have used systems such as ChatGPT, Copilot, Grok and Gemini as thinking partners, development assistants, research helpers, writing support and code review tools while building the platform.

TXTWRK is not ignoring the AI era; we are building around it. The platform direction includes AID by TXTWRK, AI support in the post box, AI-assisted research, safer posting, translation processing, summarisation, content review, checklist help, feedback analysis and structured output generation.

External AI tools can already connect conceptually through reader actions such as Ask ChatGPT, Ask Copilot, Ask GROK, Gemini and Download .TXT. Download .TXT gives users a simple export when an AI tool cannot read a page directly.

The future AI direction includes voice commands, auto-scroll, follow-up questions while reading, researching around a post, moving through comments, adding ideas to the post box and helping users process long pages without losing context.

The translation strategy belongs here too. Rather than forcing every browser to run heavy frontend AI, we prefer backend-assisted translation processors that can populate language fields where appropriate.

Students, organisations, learning records and public experience

TXTWRK for Education presents the platform as public working technology for students, institutions, organisations, artists, entrepreneurs and volunteers.

The education route centres on students documenting work experience with organisations. A student can use profiles, posts, checklists, comments, files, replies, timetables, to-dos, events, outcomes and reflections to show actual work.

Organisations can create profiles, open checklists, invite volunteers or students, monitor applications and use API support where external file hosting is needed.

Education also connects to Textbook local proofs, community libraries, public knowledge and open-source world building.

Account control, data accounting, safety and transparency

Account Control gives users an overview of their data and activity. It can count profile covers, profile photos, follows, labels, business addresses, Info Reels, post types, engagements, interactive engagements, checklists, chats, saves, API kits, monetisation and protected posts.

Fair usage and data accounting protect the network. We track post media data through values such as total post data bytes, remaining user bytes, picture size, voice size, MP3 directory size, CSV/location size, story size, video size and 3D asset size.

Safety is a core layer. Users need control over visibility, blocking, take-break states, reporting and interaction boundaries. Activity systems should respect safety filters so users do not see activity connected to post owners or notification actors they should not see.

Projection controls support transparency. Users should know whether a post can appear in feeds, media reels, local discovery or other areas.

Super Admin, trending topics and platform operations

The planned Super Admin Panel will centralise segmented admin tools into one power area. It can grow toward many tools for network maintenance, trending topics, page posting, automation, checks and operational tasks.

A key principle is a network-load check before selected admin tools or actions run across the network. The tool list should default to all selected, with admins able to deselect items before proceeding.

Trending Topics automation helps identify, label, add and manage topics, including clearer rows, result labels, used counts, added dates and last-used dates. This adds discovery intelligence because the network can understand what people are connecting to.

Official page contribution also fits here: approved users should be able to contribute to pages safely without accessing the main account.

Homepage zones, web impressions and modular layout

The homepage and wider TXTWRK layout are moving toward modular zones. Left-zone widgets can include daylight hours, weather, Textbook local proofs, web impressions and other useful services.

This modular layout lets new tools appear without rebuilding the whole page. It matches the API kit approach: useful modules can live inside TXTWRK and also become embeddable elsewhere.

Web Impressions are visual storytelling modules. They can explain education, feedback, activity, local proof, AI support, community knowledge or the network as a living system.

We are leaving the top About page web impression out for now so it can be designed properly after the written structure is right.

Data preservation, community library and long-term memory

Data preservation is one of the deeper aims of TXTWRK. Profiles, posts, checklists, community content, public work, donations, investment context, feedback and knowledge records should not vanish casually.

Community Content and Community Library concepts allow useful content to be shared, organised and preserved. Over time, TXTWRK can become a public learning base where posts, files, feedback, checklists, questions and knowledge records are connected.

Legacy Forever API supports this direction by preparing for long-term preservation across partner networks and domains. Public user data and meaningful records should survive beyond one temporary service cycle.

Individuals, organisations, communities, developers and services

TXTWRK is for individuals who want a profile, a memory base, a working record and a way to publish more than casual updates.

It is for organisations that want profiles, checklists, feedback, opportunities, addresses, timetables, products, public work, applications and transparency.

It is for communities that need local discovery, street feedback, events, maps, public proof, pledges, volunteering and visible issues.

It is for developers who want code playgrounds, API kits, external widgets, server tools, file access and domain-connected services.

It is for education providers, creators, local businesses, public services and civic groups that need better records, signals and participation routes.

Why TXTWRK is more than a social feed

TXTWRK is different because it combines identity, work, media, proof, feedback, local data, AI support, monetisation, APIs and preservation into one platform.

Most platforms focus on one lane: posting, messaging, commerce, maps, education, files or websites. TXTWRK connects those lanes so public work can move between them.

A post can become evidence. A checklist can become education. Feedback can become local proof. An address can become a map point and an external widget. A profile can become a public work base. An API kit can make the record portable.

Latest development direction

The current direction is to round off the platform into a clearer, more powerful system: stronger About/Education pages, cleaner widgets, better API kits, stronger activity discovery, media projection, admin tooling, contributor access, AI support, product display, translation processing and account control.

Near-term priorities include Events, Addresses, Feedback and Linking API kits; profile product display; Super Admin panel; Trending Topics automation; approved page contributors; Media Reels projection; fair data accounting including 3D assets; and Web Impression modules.

Long-term, TXTWRK should become a public working network that helps people build profiles, publish evidence, organise community work, preserve knowledge and connect their own websites to useful public infrastructure.