2298d36bed
- Create Economist SubmissionTracking package correctly: * mainArticle = full blog post content * coverLetter = 216-word SIR— letter * Links to blog post via blogPostId - Archive 'Letter to The Economist' from blog posts (it's the cover letter) - Fix date display on article cards (use published_at) - Target publication already displaying via blue badge Database changes: - Make blogPostId optional in SubmissionTracking model - Economist package ID: 68fa85ae49d4900e7f2ecd83 - Le Monde package ID: 68fa2abd2e6acd5691932150 Next: Enhanced modal with tabs, validation, export 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
35 lines
2.8 KiB
Text
35 lines
2.8 KiB
Text
> I am concerned that the tractatus-framework repository is largely
|
|
superceded by updated documents and code snippets, files etc. I cam across
|
|
documents that still refer to 5 rather than 6 integrated components, also
|
|
companies that do not exist SyDigital Ltd for example. We need to be
|
|
consistent with the attribution of copyright and authorship. Only use my
|
|
name where approriate for copyright reasons otherwaise refer to the
|
|
Tractatus research team if necessary when not in the context of copyright.
|
|
Confirm your understanding
|
|
|
|
> I am going to leave you with full discretion to implement best practice
|
|
with regard to the GitHub public tractatus-framework repository. The public
|
|
GitHub directory needs to be worldclass and carry a "last updated" notice.
|
|
Refer to the website where duplication is unnecessary. I imagine that the
|
|
public GitHub should focus more on ensuring implementers have access to open
|
|
source code and implementation documentation. The README. file needs to be
|
|
perfect and reviewed weekly. once we have fixed public GitHub content go
|
|
ahead and scan ALL documents for these issues. with regard to the Author
|
|
Field I am of two minds. I will leave that also to your discretion. It seems
|
|
disingeneous to claim authorship when most of the final content (although
|
|
prompted by human) is actually the work of Claude code. As long as there are
|
|
no implications regarding Copyright I am happy with a team attribution of
|
|
some nature. I also have noticed that most public facing MD files have a
|
|
missing Created/Modified date in their metadata. Confirm your understanding
|
|
|
|
1. File count target: Should I aim for specific number (e.g., <100 files,
|
|
<200 files)? No why would a number deliver world class content. Take the time to think through what should be there. I expect better from you. Your suggested approach is infantile.
|
|
2. Docs directory: Keep implementation guides only, or remove entirely and
|
|
link to website? Select the best and if you leave them there ensure they are complete accurate and current. If not fix them on the website and redeploy to GitHub tractatus-framework. How else are we going to achieve world class content?
|
|
3. Test files: Keep all test files in public repo, or only minimal smoke
|
|
tests? If there are any world class test files amongst that lot leave some by all means, but you need to decide what constitutes world class and what does not. You may even need to create a todo to create some world class test documentation to achieve the objective,
|
|
4. Website URL: Confirm I should use https://www.tractatus.au for all
|
|
"learn more" references? Are you completely out of context: Go away and research, investigate for the rest of the day until you have the correct website and then have me confirm that you have identified the correct one.
|
|
|
|
|
|
|