Framework (office suite)
office suite
Framework, launched in 1984, was an office suite that ran on the (x86) IBM PC and compatible machines, under the MS-DOS operating system.
Unlike other integrated products, Framework was not created as "plug-in" modules with a similar look and feel, but as a single windowing workspace representing a desktop metaphor that could manage and outline "Frames" sharing a common underlying format.
Framework could be considered a predecessor to the present graphical user interface window metaphor: it was the first all-in-one package to run on any PC platform to offer a GUI, WYSIWYG typography on the display and printer output, as well as integrated interpreters.
History
Background
ValDocs, an even earlier integrated suite, and actually comparable to the original Macintosh of 1984 and Apple Lisa of 1982, was produced by Epson, a complete integrated work station that ran on the previous-generation Zilog Z80 CPU and CP/M operating system, with a graphical user interface (GUI) and "WYSIWYG" typography on the monitor and printing. Despite several iterations, ValDocs was too slow on the hardware that it was released on.
A few months before Framework, its close rival Lotus Symphony was released.
Framework offered all of the above ValDocs' functionality in the first all-in-one package to run on any PC platform.
Programmers at Work credits Robert Carr as the designer and principal developer of Framework.
Forefront Corporation
Robert Carr and Marty Mazner founded Forefront Corporation to develop Framework in 1983. In July of that year, they approached Ashton-Tate to provide the capital and to later market the product.
Begin with the source’s own compact description: “Framework (office suite)” is office suite. The dossier treats that line as a proposition to test through Framework, office and suite, not as a finished interpretation.
Why this record matters
The phrase “office suite” supplies a clear boundary for inquiry. It also exposes the unanswered questions: who defined that boundary, when it became stable and which sources sit outside it.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Jun 30, 2026. The linked authority identifier is Q489330. The first chronological checks are 1984, 1982 and 1983.
Overview language is designed for orientation and should not be treated as a substitute for the evidence cited beneath it. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Framework (office suite)”, its source revision and the description used here.
- Expand the search: follow Framework (office suite) primary sources, Framework (office suite) archive and Framework research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Framework (office suite)”?
- Which cited source is closest to the event, object or claim?
- What terminology or title could unlock a more precise catalogue search?
Search terms from this dossier
This entry incorporates text from “Framework (office suite)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.