CLI: Reimplement "draft" command

[martinhalford]

Feature Request 🛍️

The draft command was recently removed from the latest unstable version during the removal of Ergo. As discussed at Tech Working Group meeting on Wed 18 Oct, we'd like to reimplement the draft command back into template-archive until such time as it can be implemented in a future accord CLI app.

Use Case

• Allow users to merge a template with data in order to produce a draft agreement/contract. This is, most likely, for testing purposes only.

Possible Solution

• Reimplement the CLI code.
• Add template-engine code to perform draft functionality, as the cicero-core package no longer contains this capability.

[martinhalford]

@mttrbrts @dselman - I have re-added the CLI args etc and am now up to the bit where we call template-engine.

Can you please share the REPL with the sample code that demonstrates how to implement the draft functionality?

I tried this one.... https://replit.com/@dselman/AccordProjectTemplateEngine-Hello-World?v=1#index.js

However, I get the error ERROR: TemplateMarkInterpreter is not a constructor when I try to.... const engine = new TemplateMarkInterpreter(modelManager, {});

Any pointers gratefully accepted!

Thank you!!

[kunal-595]

Hi @martinhalford,i would like to work on this issue ,Could you please assign it to me if it’s still available?

[Aradhana2803]

Hi , @martinhalford

I’ve gone through the issue details and related discussions (#800, #801), especially the context that:

The original draft command was removed along with Ergo,

cicero-core no longer provides draft functionality,

The feature now needs to be reintroduced inside template-archive,

And the remaining challenge is wiring the CLI layer to the new template-engine APIs (since TemplateMarkInterpreter is no longer constructed the same way).

My understanding of the current blocker

From your comment, the error

TemplateMarkInterpreter is not a constructor
suggests that the template-engine API changed after the Ergo removal and the old REPL example is outdated.

To move forward, the draft function likely needs to use the newer TemplateMark processing pipeline — similar to how parse and generate are handled now — instead of the old interpreter constructor pattern.

Proposed Contribution Plan

If the approach above aligns with the maintainers’ intent, I’d be happy to contribute. My plan would be:

Review the current template-engine API to identify the correct draft-call workflow.

Reintroduce draft in template-archive by:

Connecting the template + data → TemplateMark → rendered output pipeline.

Rebuilding the CLI layer matching the latest structure.

Test against existing example templates to ensure compatibility.

Add/update documentation to reflect the new behavior.

If this issue is still open for contribution, could you please confirm and assign it to me?
I’d be glad to proceed with a PR after approval.

Thanks!

[Kgupta62]

Hi 👋

I’d like to work on this issue and add the MongoDB version check instructions to the README for Ubuntu users.
I have 2+ years of industry experience in a product-based company, have contributed to multiple open-source projects, and have hands-on experience working with MongoDB.

Please assign this issue to me so I can start working on it and submit a PR.

Thanks!