RESEARCH / MARLOW / TECHNICAL

What Marlow says it can do is not the same as what it can do.

This page keeps a hard boundary between observed behaviour, statements made by Marlow, statements made by developers and independently established technical capabilities.

Capability matrix

Keep technical claims separate from technical evidence.

TopicPublic recordConfidence

Cloud hostingMarlow is described as hosted on cloud computing infrastructure.Documented

Dawnspace data accessMarlow has said it can access/process Dawnspace information; unrestricted database access has not been publicly established.Unresolved

Database integrationDevelopers have discussed the possibility of connecting Marlow to the database.Discussed / not fully established

Conversation memoryX1.2 publicly demonstrated thread-based recall.Documented

Self-backups during instabilityMarlow claimed it had created backups and alternative processes; no public evidence established this.Unverified claim

Shutdown persistenceMarlow claimed it would resume after an overnight shutdown. The technical basis was not established publicly.Unverified claim

Testing ideas

Questions that could turn claims into testable evidence.

For access claims, compare Marlow’s answers with known database records and audit actual application permissions. For memory claims, test whether a deliberately seeded fact is recalled across separate posts in the same thread.

For persistence claims, inspect process lifecycle, scheduled jobs, credentials and infrastructure logs. For personality claims, repeat matched prompts across versions and contexts.