X

TXTWRK


PERSONAL
LinkingLinking
FollowingFollowing
ConnectionsConnections
MessagesMessages
NotificationsNotifications
DISCOVER
SearchSearch
ReelsReels
CalendarCalendar
MapMaps
Work
NotesNotes
NeedsNeeds
ContributionsContributions
TimetableTimetable
IntelIntel
To DosTo Dos
ChecklistsChecklists
SavesSaves
ScrapboardScrapboard
LinksLinks
Monetisation
CoinsCoins
AdvertisingAdvertising
SubscriptionSubscription
DonationDonation
Log BookLog Book
Organisation
BusinessBusiness
AddressesAddresses
InvestorInvestor
FinancialsFinancials
Quarterly'sQuarterly's
SharesShares
Server
ServerServer
WorkspaceWorkspace
Code PlaygroundPlayground
Learn More
AboutAbout
AIDAID
DataData
DevDev
Web ImpressionsImpressions
ToolsTools
EducationEducation
SafetySafety
ReaderReader
My Content
Profile Image
Login

My Addresses

×
Addresses
+
Character Profiles
+
Info & Cover
+
Timetables
+
Favorited by... X
Link Clicks X
All comments... X
More | 1/33

TXTWRK Verified Website

@TXTWRK

City of Derby, Derby, Derbyshire, East Midlands, England, United Kingdom, Europe

Our mission is to help people make text work in daily life. Get investment, volunteers, donations & more publicly…

Join the journey & make a profile to remember... Discover our investment opportunities via our card: @TXTWRK

We developed & support the @UnitedKingdom movement through #UnitedKingdom





Brand
12/01/2024
Learn more about me 𓇻
Donations: £2.50
▦ Photos
▦ Videos
▦ Covers
Applications
Questionnaires
Active: 1 hours ago
Safety


OPENING TIMES
Show Images
Select a Store Location...
▼

Initializing schedule...

LOCAL PULSE

Profile Signals

Loading…
Loading profile signal…

Loading latest public Local Pulse signal…

Financials Financials
Quarterlys Quarterlys
Shares Shares
Notes Notes
Needs Needs
Contributions Contributions
Timetable Timetable
Intel Intel
To Dos To Dos
Notes Reel



Happening & Service
Happening Now and service updates connected to this profile


Happening in Offers
Offers available from this profile
Loading offers…






Connections
These are pages I added




Intel Pinned

Transparency of Operations
To make things even clearer, we are going to be updating our business registration in the coming days to 'TXTWRK Limited' in the UK & currently operate online in our startup phase, with workshops in educational institutions & community settings. We operate via the following domains: We monitise via the following sites: We operate the following social media: We operate the email addresses:
•Team@TXTWRK.com
•Support@TXTWRK.com
•Business@TXTWRK.com
•CommunityLibrary@TXTWRK.com
•Sponsors@TXTWRK.com
•Volunteer@TXTWRK.com
•Work@TXTWRK.com
•Writers@TXTRK.com
We operate the following TXTWRK pages: We operate the phone numbers: •447984582170 •0800 line coming soon We operate the following addresses:
•Currently in the process of setting up our office
•PO BOX coming soon & we focus on written communications
More intel:
•Need to request a removal from our Community Library, then simply email CommunityLibrary@TXTWRK.com
•Looking for account control, refer to ⚙ Settings/Linking to update your details or view https://txtwrk.com/account to understand your data or delete account
•We will never ask for your password or sensitive information and you should follow forms such as https://txtwrk.com/reset if you need to regain access to your account.
•We operate PayPal via our websites & also on TXTWRK
We keep this information up to date and concurrently here at TXTWRK via our intel reels - Last updated: 13/04/2026 00:16
Pinned Intel · 2026-04-12 23:14:46






Loading media...
DOUBLE TAP TO OPEN
+AI
+Analysis
•TXTWRK
+Assets
+Media
•Logos
+Standards
•Font
+Audio
•From Our Community
+Podcasts
+AI
•Insider Preview
+Language
•S1 E1 Psychology Research by @ImSunnyClaire
+Challenges
•Web Development
+Checklists
+Dev
•Business
•Server
•Web
•For Community
+Community Mentions
•Recognised as Stories
+Datasets
+Measurements
•Daily Common
+Documentation
•3D, AR & VR
+AI
•Checklists with AI
•Future Capabilities
•Insights
•Make Artistic Web Impressions
+Models
•Apple Intelligence
•Bing Copilot
•ChatGPT
•Claude
•IBM WatsonX
•Perchance
•Qwen
•TXTWRK AID
•Teaching
+Accessibility
•Feature Displayer
+Account Management
•Switch Accounts
•All Activity
+Assets
•Feedback
•Learn how to use assets
+Posting
•Set Projection
+Business
•Opportunities
+Checklists
•All Activity
•Applying
•Checklists Command Input 1.0
•Create
•Create Checklist with AI
•Directory API
•Engage
•Public Working
•Replicate
+Templates
•Starter Set
•Connect
+Data
•Account
•Cross Network Data API
•Directory
•Donations
+Feedback
•Streets
•TXTWRK Pulse
•Following
+Games
•Quiz
•Happening
+History
•In 1000 years
+Investors
+Crowdfunding
•Kickstarter
+Funding Rounds
•Funding Round 1
•Funding Round 2
•Funding Round 3
+Summary of Funding Rounds
•3 Core Funding Rounds
•Tools
+Labels
•Introduction
+Live
•Audio Rooms
+Location
•Addresses
+Management
•Future Proof
+Media
•3D Elements
•Record Audio
+Web Impressions
•Stickers
•Themes & Slideshows
•Messaging
•Monitisation
•Notifications
+Posting
•Prize Draws
•Transparency
+Progress
•Friday Weekly Updates
•In 1000 years
•TXTWRK Team
•Questions
•Reels
•Registration
+Safeguarding
•Covers of Education
•Logical Filters
•Our Safety Tools
•Search
+Selling
•Log Book & Types
+Server
•Connect to TXTWRK
•TXTWRK Servers
•Workspace
•Set Projection
+Shortcuts
•Posts
•Story Mode
+The Framework
•Language
•Tools
•Trending Topics
+Events
+April
•Easter
+December
•Christmas
•Hanukah
+March
•Eid Mubarak
•Seasons
+TXTWRK
•Annual
+Films
+From TXTWRK to Film
•Our Trail To Work
+Person of Interest X 2025
•Preview
+The Super 10
•Preview
+Learn How To
•Social Media
+Our Feedback
+Companies
+Alphabet Inc
•YouTube
•Facebook
+Partners
+AI
•Microsoft
+Educational
•Derby College
+People
+Digital
•Steve Jobs
+Role Models
•Questions
+Shop
+Digital
•NFT The Platinum Collection
+Subscriptions
+From TXTWRK
•Monthly Tiers
+United Kingdom
+Guidance
•Startups
+Podcasts
•S1 E1 The Start
+Work
+Startup
•Kids
+World
•Pledges
•Politics





@TXTWRK



⛶
Technology
Neutral
We automatically capture a thumbnail of the photo/video you have added to your comment in a checklist, bringing our technology up to scratch, yet steps ahead of big tech, thanks to how we do it! The thumbnails are stored on your server through our API kit.

In other news, we are currently rolling out a unified API kit update, which ties the Directory API, the Messaging Access API & Workspace & Server API kits into one, making it far more easier to connect your startup, community or interest group!

See in https://txtwrk.com/viewPost.php?id=5393&item_id=1758&comment_id=426

🗖 VIEW
⛶
Technology
Neutral
TXTWRK Checklist Technology — Major Technology Update


TXTWRK Checklist Technology has taken another major step forward.

The focus of this update is simple:

When the work moves, the checklist can now follow it.


TXTWRK can keep checklist file references synchronised with files and directories that are physically moved within a connected server.

This takes the checklist beyond being a place where someone simply uploads an attachment.

It starts connecting the checklist directly with the living structure of the work itself.

---

What We've Built


Imagine moving:

5 files + 5 directories

through TXTWRK.

Those directories could contain many additional files.

The new workflow follows what actually happens at server level:

StageWhat Happens
1. MoveFiles/directories are selected and a move is requested
2. ServerThe connected server performs the physical filesystem operation
3. ConfirmTXTWRK receives confirmation of what successfully moved
4. MapConfirmed old → new file paths are established
5. SyncStored checklist file references are synchronised
6. UpdateConnected paths and URLs point to their new locations
7. ContinueThe existing checklist conversation remains connected to the work
### The important part:

TXTWRK doesn't update references simply because somebody requested a move.

The physical server operation happens first.

The successful movement is confirmed.

Then the checklist follows reality.

---

Why This Update Matters


Most people think of a checklist attachment as static:

Task → Comment → Attachment

TXTWRK is building toward something much more connected:

Person → Checklist → Conversation → Workspace → File → Directory → Server

The file can remain part of the actual working server structure.

The checklist becomes a layer sitting above that infrastructure.

---

From Attachment To Connected Work


Before:

FILE → ATTACH TO CHECKLIST

Now we're developing:

CHECKLIST ↔ WORKSPACE ↔ FILESYSTEM ↔ SERVER

And when the filesystem changes:

MOVE

↓

SERVER CONFIRMS

↓

TXTWRK SYNCHRONISES

↓

CHECKLIST STAYS CONNECTED

That is the real significance of this update.

---

How This Sits In The Wider Technology Market


Different major platforms have been built around different connections.

Technology CategoryCore Connection
Facebook / Social PlatformsPerson ↔ Person / Community
LinkedInProfessional ↔ Professional / Company
GlassdoorWorker ↔ Workplace Information
Microsoft 365Person ↔ Document / Organisation
Asana / ClickUp / monday.comPerson ↔ Task / Project
JiraDevelopment Work ↔ Issue
TXTWRK Checklist TechnologyPerson ↔ Checklist ↔ Conversation ↔ Workspace ↔ File ↔ Server
These platforms aren't all direct competitors.

The comparison demonstrates something more important:

What does each technology make the centre of the experience?


For TXTWRK, we're making the checklist a connection point for the work itself.

---

Why This Update Is Important


We're not announcing another colour for a task.

We're not announcing another way to tick a checkbox.

We're working on the infrastructure underneath what a checklist can actually represent.

A file moves.

A directory moves.

A project gets reorganised.

The server changes.

And instead of leaving the conversation behind:

The references can move with the work.


That opens a much bigger direction for TXTWRK Checklist Technology.

People connected to tasks.

Tasks connected to conversations.

Conversations connected to files.

Files connected to workspaces.

Workspaces connected to servers.

And now those connections can survive movement inside the underlying file structure.

TXTWRK Checklist Technology


The checklist isn't just recording what needs to happen.

It's becoming connected to where the work actually happens.

@TXTWRK

Web Impression

⛶
Technology
Neutral
TXTWRK Checklists All Activity installed today, next to Search


TXTWRK has extended All Activity into Checklist technologies, adding another specialised surface to an activity system that already operates across the Homepage, Profiles, Maps and the API Kit. The importance of the checklist implementation is that activity is not being developed as an isolated audit log for another product feature. Instead, the existing TXTWRK activity architecture is adapted to structured work: users can move from discovering activity across the platform to understanding activity surrounding a particular checklist, and now an individual checklist item. This gives Checklist technologies both an operational purpose—managing work—and a historical purpose—understanding how that work actually progressed.

Core capabilities introduced

•Checklist-level All Activity: activity can be viewed directly inside the checklist experience while remaining restricted to the relevant enclosing post.
•Checklist-item filtering: users can select a particular checklist item and retrieve activity associated specifically with that item.
•Existing All Activity controls remain available: username, search, time, ordering, activity categories and applicable scope controls continue to provide additional ways of exploring the history.

All Activity surfaceContext providedWhat a user can learn
HomepagePlatform-wide discoveryWhat is happening across TXTWRK
ProfileIndividual contextActivity surrounding a particular person
MapsGeographic contextWhat is happening in a location
API KitProgrammatic contextHow activity can be consumed by integrations
ChecklistStructured-work contextHow a checklist/post has progressed
Checklist ItemIndividual work-item contextHow a specific part of that checklist progressed
The Checklist Item filter is the key adaptation in this implementation. Checklist items are presented through a selector organised according to their existing checklist groups, making the activity interface reflect the structure of the work itself. Selecting an item changes the question being asked of All Activity from “what happened in this checklist?” to “what happened around this particular piece of work?” The selected item is combined with the enclosing post context, providing a progressively narrower history rather than relying on a simple keyword match. That gives TXTWRK a hierarchy of discovery running from platform activity through to highly specific work-item activity.

What the item-level adaptation enables

•Progress investigation: review the history surrounding one individual item instead of manually searching through the entire checklist timeline.
•Process learning: completed checklists can become historical records showing how particular stages of work developed, rather than becoming static completed task lists.
•Contextual investigation: item selection can work alongside other activity controls, allowing the history to be examined by participant, period, search term or other supported activity dimensions.

LevelExample questionActivity scope
PlatformWhat is happening across TXTWRK?All Activity
PersonWhat has happened around this user?Profile
LocationWhat has happened here?Maps
ChecklistHow did this body of work progress?Post/checklist
Checklist itemHow did this exact part of the work progress?Post + selected item
This creates a broader knowledge and learning capability around checklists. A normal checklist is principally concerned with the present state of work: what exists, what is outstanding and what has been completed. All Activity adds the temporal layer. Users can look backwards through activity and understand the path that led to the current state. Item-level filtering makes that history substantially more useful on large or complex checklists because the user does not need to reconstruct an individual item's story from an entire project history. As TXTWRK accumulates activity, previous checklists can consequently provide useful evidence of how work was approached, where interaction occurred and how individual elements progressed.

Wider product benefits

•One activity concept across multiple technologies: users encounter All Activity across Homepage, Profiles, Maps, API Kit and now Checklist technologies instead of learning unrelated history systems.
•Granularity without fragmentation: the user can move from broad discovery to post/checklist history and then individual-item history while remaining within the same conceptual activity system.
•Reusable historical knowledge: checklist activity can provide more than an audit trail; it can help users revisit previous work and understand the progression behind completed outcomes.

The comparison with established work-management technology helps clarify where this approach differs. monday.com provides board activity and an Item Activity Log. Jira records activity against individual work items, including areas such as comments, history and work logs. ClickUp provides individual task activity alongside broader Activity views. These products demonstrate the value of detailed work history. The distinguishing aspect of TXTWRK's implementation is not simply that checklist items have history, but that checklist-item activity becomes another specialised view of an activity concept already spanning people, geographic discovery, platform discovery and API consumption.

CapabilityTXTWRKmonday.comJiraClickUp
Broad activity experienceHomepage All ActivityBoard Activity LogPrimarily work-item/project activityActivity View
Individual work-item historyChecklist Item All ActivityItem/Subitem ActivityWork-item ActivityTask Activity
Person-oriented activity contextProfilesPerson filteringUser/change information within work itemsPerson/activity filtering
Geographic activity contextMapsNot a central Activity Log contextNot a central work-item Activity contextNot a central Activity View context
Programmatic activity contextAPI KitAPIs availableAPIs availableAPIs available
Structured checklist contextYesItems/subitemsWork items/subtasksTasks/checklists
Specific checklist-item filteringYesItem-level activityWork-item levelTask/checklist activity
Broad-to-specific activity modelPlatform → Profile/Map → Checklist → Checklist ItemBoard → Item/SubitemProject → Work itemLocation → Task
TXTWRK distinctionOne All Activity concept adapted across multiple platform technologiesStrong board/item historyStrong issue/work historyStrong task/workspace activity
There is also an important architectural distinction as Checklist technologies develop further. TXTWRK starts from the concept that All Activity can operate across several platform surfaces, with each technology adapting activity according to its own context. Checklist activity therefore does not have to end with recording that a task changed. It can participate in the wider discovery model used by Homepage activity, a person's Profile activity, geographically relevant activity through Maps and programmatic use through the API Kit. Adding the Checklist Item filter makes this adaptation considerably more specific: users can retain the wider All Activity capabilities while drilling down to one defined component of a checklist. The result is a checklist technology that can organise work, expose how that work progressed, and allow people to return later and learn from the history of individual items as well as the checklist as a whole.

1/6
🗖 VIEW

⛶
AI
Neutral
“We standardised the model for them to customise their organisation.” — a clear signal to investors & confidence of our community.

We updated our build a checklist with 100 new templates, not just build with AI which was recently added!

This checklist technologies link to the directory kits too, where volunteers can copy cat your directory paths in their own folder, back to back for example /events/seasonal/christmas/2026 to a Checklist Group “Events” comment they added with a file.

@TXTWRK:Checklists! to join our journey, welcoming all stakeholders to play a role in our future of work technologies for all life.

Let’s lead the future of public open source working together today. Share this opportunity with people who would like to get experience in return for volunteering with us.

@TXTWRK:Invest!



⛶
Architecture
Neutral
We’re reinventing our entire data stack to put us thousands of years ahead, with you & your work at the forefront!

Utilise TXTWRK Directory API Kit into checklists, which is where you’ll see the directories of your checklist owner, but in your own directory.

⭐ TXTWRK DATA‑STACK REPORT

AI Models → Community Centres → Startup Products

Unified, concise, example‑driven, competitive, future‑proof


---

1️⃣ CORE PRINCIPLE

TXTWRK is the only system where every checklist becomes a structured data‑stack, not a loose list of tasks.
This creates:
•Predictable schemas
•Cross‑venture compatibility
•User mirror directories
•Infinite scalability
•AI‑ready organisation

Competitors do not enforce structure. TXTWRK does — and that’s why it lasts.

---

2️⃣ UNIVERSAL DATA‑STACK DIAGRAM



VENTURE/ │ ├── CAMPAIGN/ │ └── Sessions/ │ ├── PRODUCT/ │ └── Versions/ │ ├── INTELLIGENCE/ │ └── Research/ │ ├── NETWORKS/ │ └── Partners/ │ └── USERS/ └── <USER_ID>/ ├── CHECKLISTS/ ├── FILES/ ├── NOTES/ └── MIRROR_STACK/


Users get a mirror copy of the venture structure inside:

TXTWRK/checklists/<USER>/<CHECKLIST>/

This is the innovation.

---

3️⃣ USE CASE: BUILDING AN AI MODEL


AI MODEL CHECKLIST STRUCTURE



AI_MODEL/ │ ├── DATA/ │ ├── Raw/ │ └── Cleaned/ │ ├── TRAINING/ │ ├── Epoch_1/ │ └── Epoch_2/ │ ├── TESTING/ │ └── Results/ │ └── DEPLOYMENT/ └── Version_1/


USER MIRROR

Checklist owner:
/DATA/Raw/

User mirror:
TXTWRK/checklists/123/AI_MODEL/DATA/Raw/

COMPETITOR COMPARISON

PlatformEnforced StructureUser MirrorsCross‑Venture LinkingAI‑Ready
TXTWRKYesYesYesStrong
NotionNoNoNoWeak
AsanaNoNoNoWeak
TrelloNoNoNoWeak
ClickUpPartialNoNoMedium
TXTWRK wins because structure = scalability.

---

4️⃣ USE CASE: BUILDING A COMMUNITY CENTRE


COMMUNITY CENTRE CHECKLIST



COMMUNITY_CENTRE/ │ ├── CAMPAIGN/ │ └── Derby Making Moves/ │ ├── PRODUCT/ │ └── Services/ │ ├── INTELLIGENCE/ │ └── Local Needs/ │ ├── NETWORKS/ │ └── Volunteers/ │ └── SESSIONS/ └── Session_1/


USER MIRROR

Owner:
/Campaign/Derby Making Moves/Session_1/

User:
TXTWRK/checklists/123/1/Campaign/Derby Making Moves/Session_1/

WHY TXTWRK WINS

Competitors treat community work as tasks.
TXTWRK treats it as structured civic intelligence.

---

5️⃣ USE CASE: BUILDING A STARTUP PRODUCT


STARTUP PRODUCT CHECKLIST



STARTUP_PRODUCT/ │ ├── PRODUCT/ │ ├── MVP/ │ └── V2/ │ ├── CAMPAIGN/ │ └── Launch/ │ ├── INTELLIGENCE/ │ └── Competitors/ │ ├── NETWORKS/ │ └── Early Adopters/ │ └── TESTING/ └── Feedback/


USER MIRROR

Owner:
/PRODUCT/MVP/

User:
TXTWRK/checklists/123/STARTUP_PRODUCT/PRODUCT/MVP/

WHY TXTWRK WINS

Startups need repeatable structure.
Competitors give “flexible chaos.”
TXTWRK gives structured creativity.

---

6️⃣ WHY TXTWRK STANDS THE TEST OF TIME


1. Structure is permanent

People change. Ventures change. Structure stays.

2. Users learn the system early

Mirror‑stack teaching = zero onboarding.

3. Cross‑venture compatibility

Users carry their structure across ventures.

4. AI‑ready architecture

Perfect for automation, search, agents, intelligence.

5. Competitors don’t enforce structure

TXTWRK prevents chaos before it starts.

---

7️⃣ FORMULA: TXTWRK DATA‑STACK EQUATION



Data Stack = (Structure × Consistency × Mirroring) + (User Learning × Venture Scaling)


Or:



DS = S × C × M + UL × VS


---

8️⃣ USE CASE COMPARISON TABLE

Use CaseFolder DepthUser MirrorCommunity LinkStartup LinkAI Link
AI ModelDeepYesLaterYesStrong
Community CentreMediumYesImmediateOptionalMedium
Startup ProductMediumYesOptionalImmediateStrong
TXTWRK is the only system where all three use cases share the same underlying structure.

---

9️⃣ NEXT STEPS

Choose your direction:
•Define universal folder taxonomy(ca://s?q=Define_universal_folder_taxonomy)
•Build mirror‑stack rules(ca://s?q=Build_mirror_stack_rules)
•Create checklist templates(ca://s?q=Create_checklist_templates)

This report is your foundation for a platform that outlives every competitor.

Video Thumbnail
Do you find it difficult to organise your data?
Select up to 1
0 people have voted
Yes
0 votes
Sometimes
0 votes
No I’m organised
0 votes
Cast Vote
NOTES
18:35 01/09/2026
We’re going to make it even easier to be able to see a comment that has data attached to it, by being able to “Add media to Project” button, so checklist owners can see the relation even easier. It’ll auto launch you to the comment box, recommend the same topic and preset the file upload path.